Business Strategy

Purpose: Capture market positioning, revenue model, and go-to-market insights. Last Updated: April 2026 Status: Pre-pilot validation phase

Portfolio Context

docus.ao is a product of Exponencial Lda. (exponencial.ao), part of a portfolio strategy.

Strategic Value to Exponencial

Value Type	Description
Recurring Revenue	Predictable MRR vs project-based income
Market Presence	Always-on product keeps Exponencial visible
Cross-Sell Engine	Customers need other services (dev, consulting)
IP Asset	Sellable/licensable independently if needed
Credibility	”We build and run our own SaaS” signals capability

Cost Advantage (Shared Infrastructure)

As a portfolio product, docus.ao benefits from:

Shared dev team (marginal hours, not full allocation)
Shared support (Exponencial team handles)
Shared infrastructure costs
Exponencial brand halo for marketing

Effective break-even: ~$500/month MRR (~10-15 customers across entity tiers + overheads)

The Problem

Companies in Angola (and globally) struggle with:

Documents scattered across email, drives, filing cabinets, and people’s heads
Last-minute scrambles for tenders, audits, bank loans, and partnerships
Discovering expired or missing documents at critical moments
No single view of “are we compliant?”

The cost of failure:

Lost tenders worth millions
Fines for expired licenses
Delayed financing
Staff hours wasted hunting for documents

Value Proposition

One-liner: Know instantly if your business documents are valid and ready.

Transformation: Reactive Panic → Proactive Readiness

Core question we answer: “Do we have a valid document?”

What we’re NOT: A general Document Management System (DMS), file storage, accounting, or ERP. We do not manage the drafting or editing of documents. We strictly centralize final, distinct legal artifacts (certificates, licenses, IDs) to make them findable and packageable.

Target Market

Primary: Angolan businesses with heavy compliance burdens

From SMEs to large enterprises — sized by tracked entities (people, vehicles, equipment, properties), not headcount; no upper bound
Industries: Oil & Gas services, Construction, Logistics, Trade/Import-Export
Pain: Heavy bureaucratic compliance requirements
Budget: $25-2,000+/month range, scaling with tracked entities (progressive pricing)

Beachhead Vertical: Oil & Gas Services

Highest document burden (ANPG, HSE, insurance, etc.)
High-value tenders where compliance is mandatory
Established procurement processes that demand document packs
Willing to pay for operational tools

Expansion Path

Angola (first market / proving ground) → international, with Lusophone Africa (Mozambique, Cape Verde, Guinea-Bissau) the natural first step → worldwide as the model validates
Single company → Multi-entity groups
Document tracking → Tender response automation

Competitive Positioning

Real Competition

Excel + Google Drive + Email chaos (the incumbent)
Not other document software

Why We Win

Factor	Excel/Drive	docus.ao
Knows documents expire	No	Yes
Alerts before expiry	No	Yes
Knows what’s missing for a tender	No	Yes
One-click document bundle	No	Yes
Angola-specific doc types	No	Yes

Defensible Moat

Local regulatory knowledge (AGT, INSS, ANPG document types)
Pre-built Smart Pack templates for common scenarios
Network effects if we become the “compliance handshake” between companies

Trust Signals

Critical for Oil & Gas and government-adjacent customers.

Data Sovereignty

Hosted on Supabase (AWS infrastructure)
Data encryption at rest and in transit
Can discuss dedicated instance for enterprise

Audit Trails

Every document view logged (who, when)
Every download logged
Every share link tracked
Exportable audit report for compliance officers

Security Messaging

“Your documents are encrypted and access-logged”
“See exactly who viewed your Alvará and when”
Feature Excel/Drive doesn’t have

Revenue Model

Pricing Evolution: How We Reached This Model

The pricing model evolved through three stages as we deepened our understanding of how value scales in compliance document management.

Stage 1: Employee-Band Tiers ($25/$50/$100 by headcount) The starting model. Analysis revealed a fundamental misalignment: platform users (~3-5 people managing documents) are constant regardless of company size. What scales is the number of tracked entities — employees, vehicles, equipment, and properties whose compliance documents multiply with business scale.

Stage 2: Named Plans + Entity Quotas (Essencial $39 → Empresa+ Custom) Fixed entity quotas per named plan. Better than employee bands, but created cliff edges: jumping from 75 to 300 entities meant jumping from $99 to $249 even if you only needed 80 entities. Plan names also added friction — prospects spent time comparing plan features (there were none to compare — all features are included) instead of evaluating value.

Stage 3: Progressive Per-Entity Pricing (current model) Inspired by Kaspersky managed services licensing and similar models (CodeTwo, Dropsuite). Eliminates cliff edges entirely. Even a 3,000-entity customer pays full rate on their first 10 entities. Discounts apply only to entities above each threshold — like income tax brackets.

Five models were evaluated:

Model	Mechanism	Outcome
Employee-Band Tiers	Price by headcount ($25/$50/$100)	Rejected — value scales with entities, not employee count
Document Volume Tiers	Price by active document count	Rejected — gameable (“delete 100 docs before payday”), abstract metric
Base + Per-Entity (flat)	$39 base + $2/entity/mo	Rejected — variable bills harder for enterprise finance to approve
Named Plans + Entity Quotas	Familiar named tiers (Essencial → Empresa+)	Rejected — cliff edges between tiers, plan names add unnecessary friction
Progressive Per-Entity	Tax-bracket rates, no plan names	Selected — smooth growth, fair at every scale, self-serve calculator

Why entity-based pricing won over document counting:

Entities (people, vehicles, equipment) are stable and verifiable — you can’t pretend you don’t have 3000 employees
Documents per entity are unlimited (up to 100), which incentivizes MORE uploads (increases stickiness, not cost)
“How many employees and vehicles do you have?” is easy for any prospect to answer
Entity count doesn’t fluctuate month-to-month like document count
Document-count metering was specifically rejected: it’s gameable

Two-Bucket Document Taxonomy

All document types are classified into exactly two scopes via a scope field on the document_types table:

Company documents (scope = ‘company’)

Belong to the legal entity itself (Alvara, NIF, INSS clearance, AGT certificates, insurance policies, company presentation, financial statements, etc.)
27 types across 7 categories (legal, tax, social, operational, insurance, commercial, institutional)
Unlimited at every pricing level, including the future free tier
Do not count toward any entity quota
These are the “hook” — every business has them, value is immediate

Entity documents (scope = ‘entity’)

Belong to a tracked entity: a person, vehicle, equipment item, or property
17 types across 2 entity categories (personnel: 13 types, fleet: 4 types)
Future expansion: equipment and property entity types
Count toward the entity quota that determines price
Hard limit: 100 documents per entity (all types combined, excluding versions)
These are the “revenue engine” — the more entities tracked, the higher the price

→ See DATA_MODEL.md for scope field on document_types → See DOCUMENT_TYPES.md for full type inventory (40 types)

Progressive Per-Entity Pricing

Rate tiers (progressive — each tier applies only to entities in that band):

Tier	Entities	Rate per entity/mo
1	1–10	$2.50
2	11–25	$2.20
3	26–50	$1.90
4	51–125	$1.60
5	126–250	$1.30
6	251–500	$1.00
7	501–1,000	$0.80
8	1,001–2,500	$0.75
9	2,500+	$0.70

Minimum price: $25/month (floor for any paid customer, even if tracking only 1-3 entities).

Note: Specific rate points ($2.50, $2.20, etc.) and tier boundaries are subject to partner review and may be adjusted. The architectural decision is progressive pricing; the exact numbers are tuning knobs.

Why progressive over flat buckets:

No cliff edges. Adding one entity never triggers a sudden price jump.
Fair at every scale. Large customers don’t get a blanket discount on their first entities. Banco BIC (3,000 entities) still pays $2.50/entity on their first 10.
Self-serve pricing. A simple calculator on the website: enter employees + vehicles
- locations = total entities = monthly price. No plan names to decode.
Smooth growth. The upgrade from 50 to 51 entities adds $1.60/month, not a $150 plan jump.

Website Pricing Calculator

Three input fields on the pricing page — no plan comparison tables:

Employees (people): ___
Vehicles (fleet): ___
Locations / equipment: ___
= Total entities: __ → Your price: $__/mo

The calculator shows the tier breakdown visually (coloured bar showing how much of the price comes from each rate tier). The price grows smoothly as entities are added.

What’s Included at Every Paid Level

All features: Smart Packs, OCR, alerts, reports, audit logs, knowledge base, document versioning, compliance resolution flow
Company documents: unlimited (scope = ‘company’)
100 documents per entity (hard limit, excluding versions)
Email and SMS alerts (admin-configurable per user)
Internal Users (licensed seats): scaled with entity count (see below). Role assignment (admin / manager / user / Monitor) is controlled in-app by customer admins; billing is a single per-user quota.

No feature gates. The only variable is how many entities are tracked.

Key Definitions

Tracked entity: Any person, vehicle, equipment item, or property registered in the system whose compliance documents are tracked. Company-level documents (Alvara, NIF, INSS clearance, AGT certificates, etc.) are always unlimited and do not count toward the entity quota. Entity types include but are not limited to:

People (employees, contractors, drivers)
Vehicles (company fleet)
Equipment (construction, industrial, safety)
Properties (offices, warehouses, sites)

Legal entity: A registered company/subsidiary identified by a NIF. Multi-entity accounts allow holding companies to manage subsidiaries from a single account.

Scaled Inclusions

Internal Users and legal entities scale with the total entity count. A company with more entities naturally needs more users and may operate multiple subsidiaries.

Why a single quota: Real cost drivers are support volume and SMS alerts, both of which scale with the count of licensed internal users regardless of role. Billing is one per-user quota; role assignment (admin / manager / user / Monitor) is handled in-app by the customer’s admin. External pack recipients (future Smart Pack Shared Viewer) do not count against this quota and are not priced — they don’t consume SMS or meaningful support. See DECISIONS.md § DEC-033 and USER_ROLES_PERMISSIONS.md.

Entity Count	Included Internal Users	Legal Entities
0 (free tier, post-PMF)	4	1
1–10	15	1
11–50	20	1
51–125	30	2
126–250	60	3
251–500	90	4
501–1,000	120	5
1,001–2,500	175	7
2,500+	250	10

Add-on	Price
Extra Internal User seat	$5/mo each
Extra legal entity	$29/mo each
SMS budget top-up	Deferred — price-set post-pilot based on consumption data

Flat add-on rate: $5/mo per user regardless of role. The role a seat holds determines in-app permissions and SMS defaults (see below), not the bill.

User Roles & Billing

Billing model: one seat per internal user, role-agnostic.

All licensed users count as Internal Users for billing purposes. Role is assigned in-app after the seat is provisioned — the price is the same whether the user is an admin, manager, user, or monitor. Real cost drivers are support volume and SMS alerts, both of which track the count of internal users regardless of role.

External pack-share recipients (public or credentialed links to auditors, banks, clients) are a separate concept handled by the Smart Pack Shared Viewer roadmap — they are not seats and do not count toward the Internal User quota.

Role hierarchy (assigned in-app):

Role key	Label	Typical use
`admin`	Administrator	Owns company settings, billing, invites, alert config. SMS on by default.
`manager`	Manager	Full document CRUD, applicability, Smart Packs. SMS off by default.
`user`	User	Upload and view documents, soft-delete own uploads. SMS off by default.
`viewer`	Monitor	Read-only compliance monitoring with export and audit logging. SMS off by default.

Full capability matrix, permission keys, and RLS behavior: USER_ROLES_PERMISSIONS.md. See DECISIONS.md § DEC-033 for the unified-billing and Monitor rename rationale.

SMS Alert Strategy

SMS alerts are included at every paid level — not a separate pricing dimension. SMS is off by default for most users; admins opt specific users in. This keeps SMS exposure bounded without capping how many people can hold a seat.

Default behavior:

Admins: SMS on by default for critical alerts (7-day warning and expired).
Manager / User / Monitor: Email only by default. Admin can enable SMS per individual user in Settings → Users.
30/60/90-day warnings: Email by default for everyone; admin can enable SMS per user for these too.

The SMS budget (entity-indexed):

The included SMS budget scales with the number of billed entities — the same driver as the plan price. Pool is account-level, shared across all users with SMS enabled, and resets monthly. When exhausted, remaining alerts fall back to email automatically — no overage charges. Admins see a usage meter in Settings → Alerts and get a notification at 80% consumption.

Formula:

Free tier: 0 SMS included. Email-only alerts.
Paid tiers: 1 SMS per billed entity per month, with a floor of 25 SMS/month on any paid plan. The floor ensures single-entity paid customers on the $25/mo plan still get a meaningful SMS allowance.

Examples:

Billed entities	Included SMS / month
1 entity (paid)	25 (floor)
10 entities	25 (floor)
30 entities	30
100 entities	100
500 entities	500
2,000 entities	2,000

Add-on (post-pilot): Customers whose monthly alert volume exceeds their pool can purchase an SMS top-up pack instead of falling back to email. Launch SKUs are 100 / 250 / 500 SMS packs. Pack prices to be set after pilot consumption data lands — target retail ~$0.02 per SMS (~1.75× Kwenda (SMSPro) Pacote Crescimento COGS; see VENDOR_COSTS.md).

Why this model works:

Cost-honest. SMS COGS tracks alert volume, which tracks entity count. Billing and included SMS now use the same driver.
No band edges. Band-based counts (e.g., 100 / 300 / 500) over-serve the low end of a band and under-serve the high end. Entity-indexed counts are continuous.
Admin-only default bounds worst-case spend. Typical small-plan usage lands well inside the included pool.
Per-user opt-in routes critical SMS to the right people (safety officer, HSE lead) without blowing the pool on low-priority recipients.
Fallback to email is graceful and transparent — no billing surprises, no alerts dropped.
25 SMS/month floor protects the $25 entry price. Without the floor, a 1-entity paid customer would get 1 SMS/month — mathematically correct, commercially punitive.

See DECISIONS.md § DEC-034 for the rationale behind switching from band-based to entity-indexed SMS budgeting.

Document Cap Policy

“Unlimited company documents” (DEC-026, two-bucket taxonomy) is the customer-facing promise and is preserved. Below that promise, two guardrails bound pathological usage without touching normal compliance use.

Caps:

Scope	Soft cap	Hard cap	Behavior
Company documents (per legal entity)	300	500	At 300: warning banner + archive/upgrade prompt. At 500: upload blocked.
Entity documents (per entity)	—	100 active	Already enforced.
Archived documents	—	—	Not counted against either cap.

Why this works:

300 is well above any real SME’s legitimate company-doc count (typical Angolan SME has 15–40 active company docs across Alvara, NIF, INSS clearance, AGT certificates, etc.).
Archiving is the release valve. Customers who hit the soft cap archive old versions and immediately drop below it. This rewards good hygiene instead of penalizing it.
Company-doc uploads that bypass the archive flow (e.g., dumping an entire scanning output folder) hit the hard cap quickly and surface a clear message — failure is loud, not silent.
The cap is a cost guardrail, not a feature gate. Customers with legitimate need for more (e.g., large holding companies) can add legal entities or move to custom pricing.

Implementation: DB CHECK constraint at hard cap; frontend warning state at soft cap. See SPRINT_SOW Sprint 3.

Upload-Size & Image Policy

Per-upload size caps and automatic image normalization protect storage + bandwidth cost without affecting normal compliance scans.

Limits:

File type	Per-upload limit	Normalization
PDF	25 MB	None (stored as-is)
JPG / PNG / HEIC	10 MB	Auto-resized to 2,000 px longest edge on upload; original discarded
Other	Blocked	—

Rationale:

Certificate and license scans are typically < 5 MB as PDF; 25 MB is a generous ceiling that blocks only pathological uploads.
2,000 px is legible for audit review (readable text at document-scan density) and drops typical 30 MP phone photos from ~8–12 MB to ~500 KB–1 MB without visible quality loss.
Discarding the original after resize is essential — keeping originals defeats the cost purpose. Thumbnails are derived from the resized asset.
HEIC is accepted for iPhone uploads but server-side converted to JPEG before storage for consistent downstream handling.

Failure mode: Over-limit uploads are rejected at the upload boundary with a clear error (PT-AO and EN) directing the user to compress the PDF or use a lower-resolution camera setting. No silent truncation.

Implementation: Upload middleware enforces size at ingress; image pipeline runs sharp/jimp resize + JPEG re-encode before storage write. See SPRINT_SOW Sprint 5.

Public Pricing Page Copy

The customer-facing pricing page uses a single headline block plus a calculator, not a three-column feature-grid. Angola SME buyers expect “one price, one concierge call” — a comparison grid signals US-style self-serve pricing that doesn’t map to this market.

Headline block (launch version):

From $25 / month.

Track up to 10 entities, 15 Internal Users, 1 legal entity, 100 documents per entity, unlimited company documents for normal compliance use, email alerts, and SMS within your monthly budget.

All features included — Smart Packs, OCR, audit logs, reports.

Pricing scales with entity count. See the calculator for your specific plan — every size, including 2,500+, is self-serve.

What the page does NOT do:

No “Starter / Growth / Scale” tier names (progressive pricing doesn’t have tiers — see Pricing Evolution).
No feature comparison grid. All features are included everywhere; a grid would show identical checkmarks everywhere and confuse buyers.
No annual-discount table at launch (can add later if data supports).
No “per user” pricing callout — Internal Users are included in the entity-indexed price and adding seats is a simple $5/mo add-on, not a pricing dimension.

What the page DOES do:

Calculator widget (already specified in §Website Pricing Calculator) does the math for any entity count.
Concierge onboarding for complex setups (pricing is self-serve at every size).
FAQ block addressing: “What’s a tracked entity?”, “What’s the difference between company and entity documents?”, “What happens if I go over the SMS budget?” — these are the three questions pilot prospects are asking.

See DECISIONS.md § DEC-034 for the pricing-copy rationale.

Customer Archetype Pricing (Progressive Model)

Customer	People	Vehicles	Equipment	Total Entities	Monthly Price
Small consulting firm	5	0	0	5	$25 (floor)
Trading company	30	5	0	35	$77
Construction company	80	30	100	210	$336
Oil services company	200	50	200	450	$588
Banco BIC	3,000	20	0	3,020	~$2,527

Progressive vs. old named tiers (for reference):

Customer	Old Named Tiers	Progressive	Delta
Small consulting	$39	$25 (floor)	-$14
Trading company	$99	$77	-$22
Construction co.	$249	$336	+$87
Oil services	$599	$588	-$11
Banco BIC	~$1,500	~$2,527	+$1,027

The progressive model captures more revenue from larger customers (they still pay full rate on early tiers) while lowering the barrier for small ones.

Land-and-Expand Customer Journey

This is the critical dynamic that makes progressive pricing work:

Month 1 — Land ($25/mo): Customer signs up to track company documents only — Alvara, NIF, INSS, AGT certificates. ~30-40 documents, zero tracked entities. Hits the $25 floor. Easy approval. Immediate value from expiry alerts and compliance dashboard.
Month 3 — First entities (still $25/mo): “Can we add our 5 employees’ documents?” Register 5 persons, link their IDs and training certs. 5 entities × $2.50 = $12.50, but floor keeps price at $25/mo. Still trivial.
Month 6 — Organic growth ($77/mo): Team grows to 25 employees, plus 10 company vehicles. 35 entities. Price grows smoothly: (10 × $2.50) + (15 × $2.20) + (10 × $1.90) = $77/mo. No plan jump, no sticker shock.
Month 12 — Significant value ($200+/mo): Now tracking 60 employees, 20 vehicles, 40 equipment items = 120 entities. At this point, switching back to Excel would be catastrophic. Each monthly bill reflects exactly the value being received.
Year 2+ — Large scale ($500+/mo): Growth, subsidiaries, 500+ entities. Volume discounts kick in at higher tiers. Published $0.70/entity rate for 2,500+ — still self-serve.

Each step is voluntary, value-driven, and increases stickiness. The price grows exactly with value — no cliff edges, no forced “plan upgrades.”

Free Tier Strategy (Post-PMF)

Status: Design only. Not for pilot launch. To be introduced only after product-market fit is validated, structured support processes are in place, and paid revenue is established. Target: Y2 at the earliest, after 5+ paying customers and proven land-and-expand motion.

Why not at launch:

$25/month entry point is already trivial (~22,000 AOA, cost of a business lunch)
Trust, awareness, and initial data entry friction are the real adoption barriers
Concierge onboarding (“we scan your first 50 docs”) is the launch strategy
Free users consume support capacity without generating revenue
Self-serve freemium works better after product and onboarding flow are polished

Free tier design:

Dimension	Free	Paid ($25/mo+)
Company documents	Up to 50	Unlimited
Tracked entities	0	Based on progressive pricing
Internal Users	2	4+ (scales with entities)
Smart Pack exports	View only (no PDF/ZIP)	Full export
Alerts	Email only	Email + SMS
Features	All	All
Branding on exports	Mandatory (non-removable)	Removable

Core principle: all features, zero entities. The free tier is not a feature-gated trial — it is a scope-limited version of the full product.

Natural conversion trigger: Smart Pack templates require person-level documents (shareholder IDs, manager identification, criminal records) tied to tracked entities. Without entities, these documents cannot be uploaded, and Smart Packs display structural gaps: “missing: Socio/Gerente identification.” The system honestly shows what is missing for compliance readiness. The upgrade pitch writes itself: “Add your shareholders to complete this pack — from $25/mo.”

Mandatory branding (free tier only):

PDF exports: footer “Gerado por docus.ao | exponencial.ao”
ZIP downloads: README.txt with branding
Shared links: “Organizado com docus.ao” badge with CTA
Paid plans can optionally remove branding

Angola Payment Rails

Cards are rare in Angola. Support multiple payment methods:

Invoice/bank transfer (primary for B2B)
Mobile money (Multicaixa Express) for SME
Annual billing with discount (reduces payment friction)

Additional Revenue Streams

Template marketplace — Industry-specific Smart Pack templates
Partner revenue share — Accountants/lawyers who onboard clients
Concierge onboarding — Included for larger accounts, paid add-on for smallest

Pricing Psychology

$25/mo entry point (floor) = ~22,000 AOA = cost of a business lunch. Easy approval.
All features at all levels — no “feature envy,” no feeling of being on a lesser product
Progressive pricing is intuitive: “the more you track, the more you pay, and it gets cheaper per entity as you grow”
Position against cost of: one junior admin tracking expiry dates in Excel
Enterprise pitch: “Less than one junior admin’s salary, replacing a team of 3-4”
No plan names to memorize — just a number: “How many entities do you track?”

Go-to-Market Channels

High Priority

Accountants & Lawyers - They already touch these documents monthly. White-label or referral program.
Industry Associations - AECIPA (construction), oil & gas service associations
Direct outreach - Target companies currently bidding on major tenders

Medium Priority

Banks - They require these documents for loans. Partnership opportunity.
Large contractors - Mandate subcontractors use docus.ao to share compliance docs

Low Priority (Later)

Content marketing - “Compliance checklist for Angolan businesses”
Self-serve freemium — Planned for post-PMF (see Revenue Model § Free Tier Strategy). Will serve as a self-serve acquisition channel that feeds the paid funnel through structural incompleteness triggers and branded export sharing

Channel Experiments (First 60 Days)

Channel	Target	Script/Offer	Success Metric
Direct outreach (Oil & Gas)	10 companies	”Concierge onboarding - we scan your first 50 docs”	3 pilots signed
Accountant partner	2 firms	”White-label for your clients, we handle support”	1 firm piloting with 5 clients

Concierge Onboarding (Sales Closer)

Offer: “We scan and upload your first 50 documents for you”

Purpose: Remove the #1 adoption barrier (initial data entry friction)

Positioning:

Not a paid service — it’s a sales closing tool
Offered free for first 3 pilot customers
Later: included for larger accounts, paid add-on for smallest tier

Why it works:

Customer sees value immediately (their docs, organized)
Removes “I’ll do it later” excuse
Creates commitment (sunk cost of their time reviewing)

Viral Loop: Shared Links

When a user shares a Smart Pack link (for bank loan, tender, etc.):

Recipient sees: Professional document bundle with docus.ao branding
Recipient thinks: “How did they organize this so fast?”
Recipient notices: “Powered by docus.ao” footer with link
Recipient becomes: Potential lead

Design Requirements

Shared links work without login
Clean, professional recipient view
Clear but non-intrusive branding
“Get your documents organized” CTA

Branding Tiers

Tier	Shared link branding	PDF export branding	ZIP contents branding
Free (post-PMF)	“Organizado com docus.ao” badge + CTA (mandatory, non-removable)	Footer: “Gerado por docus.ao	exponencial.ao” (mandatory)
Paid (all levels)	“Powered by docus.ao” subtle footer (removable)	“Powered by docus.ao” footer (removable)	None
Enterprise (2,500+)	Fully white-label option	Fully white-label option	None

The free tier transforms every export into a lead generation channel. Paid tiers earn the right to remove branding — creating an additional (soft) upgrade incentive for brand-conscious companies.

Key Messaging

Pain Point Hooks

“Stop losing tenders because your INSS certificate expired yesterday”
“Know your compliance status before the auditor asks”
“One click to assemble your bank loan document pack”

Feature-to-Benefit Translation

Feature	Benefit
Smart Packs	”Ready for any tender in minutes, not hours”
Expiry alerts	”Never be surprised by an expired license again”
Document status dashboard	”See your compliance health at a glance”
OCR auto-detection	”Snap a photo, we do the data entry”

Competitive Differentiation

“Your documents know when they expire. Your Drive folder doesn’t.”
“Built for Angolan compliance. Not adapted from a foreign template.”

Risks & Challenges

Technical

OCR accuracy - Must be good enough to reduce data entry, not create more work
Mobile experience - Angola users are mobile-first; Capacitor build is essential

Market

“Excel is free” objection - Win with failure stories, not features
Trust & security - Storing sensitive docs requires bulletproof security messaging
Sales cycle - B2B in Angola means relationship selling, not self-serve signups

Operational

Initial upload friction - First-time data entry is painful; must streamline
Support burden - Early customers will need hand-holding

Validation Criteria

Minimum Viable Traction

5 paying customers at $25+/month within 60 days of launch
At least 1 customer tracking 50+ entities (progressive pricing validated)
At least 2 customers actively using Smart Packs

Activation Metrics (Track These)

Metric	Target	Why It Matters
Time-to-first-upload	<5 min after signup	Measures onboarding friction
Documents uploaded in week 1	5+	Indicates adoption commitment
Pack exports per week	1+	Shows core feature usage
% expiring docs resolved after alert	80%+	Validates alert value

Signs of Product-Market Fit

Customers renew without prompting
Inbound referrals from existing customers
Feature requests focus on “more of the same” not “completely different”

Financial Projections (Angola-Only, Base Case)

5-Year Revenue Forecast

With progressive pricing, customers are segmented by entity-count band rather than named plan. The customer mix shifts up-market over time as land-and-expand dynamics take effect.

Year	Small (1-25)	Medium (26-125)	Large (126-500)	Enterprise (500+)	Total Customers	ARR
Y1	12	5	1	0	18	$14K
Y2	40	30	12	4	86	$73K
Y3	90	75	35	15	215	$200K
Y4	180	160	80	30	450	$420K
Y5	330	280	155	60	825	$780K

Note: Land-and-expand dynamics mean many Y1 small customers grow into medium in Y2 as they add entities, explaining the shift up-market over time. ARR for enterprise (500+) estimated at ~$600-2,000/mo average depending on entity count.

Unit Economics

Metric	Small (1-25)	Medium (26-125)	Large (126-500)	Enterprise (500+)
Avg. ARPU	$420/yr	$1,800/yr	$4,800/yr	~$12,000/yr
Est. CAC	$30	$100	$200	$500
LTV (3yr, 12% churn)	$1,020	$4,371	$11,657	~$29,143
LTV:CAC	34:1	44:1	58:1	~58:1

Note: Churn rate estimated at 12%. Progressive pricing creates higher switching costs — the more entities tracked, the harder it is to leave. ARPU grows naturally as customers add entities without requiring plan-level upgrades.

Marginal Cost Per Entity

Every entity added generates revenue ($0.70–$2.50/mo) but also incurs marginal costs. This table proves that margins are safe at every pricing tier:

Cost Component	Per Entity/Mo	Calculation	Notes
Storage	$0.003	100 docs × 1.5 MB × 2 versions = 300 MB @ $0.021/GB	Worst case; most entities use 8-20 docs
SMS alerts	~$0.011	DEC-034 cap: 1 SMS / entity / month @ $0.0114/SMS (Pacote Crescimento baseline, see VENDOR_COSTS.md)	Worst case — real utilization is lower since most entities don’t trigger every month
Email alerts	~$0.001	~10 active docs × 4 alerts/yr ÷ 12 @ ~$0.001/email	SMTP2Go bulk rate
Compute	~$0.001	Shared database, negligible per entity	Scales with concurrent users, not entities
Total marginal	~$0.016/mo

Rate Tier	Entity Rate	Marginal Cost	Gross Margin Per Entity
Tier 1 (1–10)	$2.50	$0.016	$2.484 (99.4%)
Tier 4 (51–125)	$1.60	$0.016	$1.584 (99.0%)
Tier 6 (251–500)	$1.00	$0.016	$0.984 (98.4%)
Tier 8 (1,001–2,500)	$0.75	$0.014	$0.736 (98.1%)
Tier 9 (2,500+)	$0.70	$0.014	$0.686 (98.0%)

Conclusion: Even at the deepest discount tier ($0.70/entity), marginal cost is ~$0.014–$0.016 — yielding a 97%+ gross margin per entity. The pricing floor is set by value perception, not by costs. There is no entity-count scale at which serving an additional entity becomes unprofitable.

Pricing philosophy: value, not cost-plus

The prices in this model are anchored to the value at risk for the customer, not to our cost to serve plus a margin. What a customer buys is not losing a tender, not paying a fine, not failing an audit — outcomes worth millions of kwanzas. We deliberately charge a small fraction of that: $2.50/entity/month (~$30/year) is trivial against the downside it protects, which is exactly what makes it approvable without a procurement fight.

Three consequences follow, and they should guide every future pricing decision:

The 97%+ gross margin is a by-product, not the goal. It results from value-based pricing meeting a near-zero marginal cost. The price is justified by value; it would be just as defensible if our costs were several times higher. We do not reason “cost + markup.”
Cost is the floor, never the dial. Cost discipline matters — it funds the company and underwrites the $25 minimum — but cost does not set the price. (This is also why the volume discount is not “passing on cost savings”: marginal cost is flat across tiers; the discount is a willingness-to-pay and fairness lever.)
Value, not cost, sets the ceiling. As the product reduces more risk for the customer, price can rise independently of cost. The real cap is perceived value × budget reality (in Angola, FX and budgets keep the absolute number modest even though the value-to-cost ratio is large) — never our cost base.

This only holds while the value is demonstrably real (the product must keep proving the cost of a miss), and sustained high margins invite entrants over time — the moat is the Angola-specific, regulator-aware positioning and switching costs, not the price.

Scale tailwind: SMS is the largest variable input, and its per-SMS COGS drops as we move up pack sizes ($0.0114 Crescimento → $0.0097 Profissional → $0.0085 Escala → $0.0080 Enterprise — see VENDOR_COSTS.md). At Tier 8, the marginal cost uses a lower SMS rate because by that scale we’re buying Empresarial or larger packs.

Marginal Cost Per Customer

While per-entity costs are negligible, per-customer costs (support, onboarding) are relatively fixed regardless of entity count. This makes larger customers dramatically more profitable:

Customer Archetype	Entities	Revenue/Mo	Infra/Mo	Support/Mo*	Contribution/Mo
Small consulting	5	$25 (floor)	$0.10	~$15	$10 (40%)
Trading company	35	$77	$0.70	~$20	$56 (73%)
Construction co.	210	$336	$4.20	~$30	$302 (90%)
Oil services	450	$588	$9.00	~$40	$539 (92%)
Banco BIC	3,020	~$2,527	$60	~$60	$2,407 (95%)

*Support costs estimated as shared Exponencial team allocation per customer. Scales with number of managers (who generate support tickets), not entities.

Key insight: Small customers at the $25 floor are marginally profitable (40%) but serve as land-and-expand seeds. The real margin engine is customers above 50 entities, where support cost is amortized across a larger revenue base.

Full Cost Structure by Year (% of ARR)

docus.ao benefits from Exponencial’s portfolio model: R&D, support, and G&A are shared resources, not dedicated hires. This dramatically reduces the cost burden in early years. As revenue scales, dedicated allocation grows.

Cost Category	SaaS Median*	Y1 ($14K)	Y2 ($73K)	Y3 ($200K)	Y4 ($420K)	Y5 ($780K)
Infrastructure	5%	$0.5K (3%)	$1.1K (2%)	$2.4K (1%)	$5.8K (1%)	$10.3K (1%)
R&D	22%	$3K (21%)	$10K (14%)	$40K (20%)	$85K (20%)	$170K (22%)
Sales	13%	$1K (7%)	$8K (11%)	$25K (13%)	$55K (13%)	$100K (13%)
Marketing	8%	$0.5K (4%)	$4K (5%)	$15K (8%)	$35K (8%)	$60K (8%)
Support / CS	5-8%	$3.5K (25%)	$10K (14%)	$18K (9%)	$35K (8%)	$60K (8%)
G&A	14%	$2K (14%)	$5K (7%)	$15K (8%)	$30K (7%)	$50K (6%)
Total Costs	~95%	$10.5K (75%)	$38K (52%)	$115K (58%)	$246K (59%)	$450K (58%)
Net Contribution	~5%	$3.5K (25%)	$35K (48%)	$85K (42%)	$174K (41%)	$330K (42%)

*SaaS median from SaaS Capital 2025 survey (1,000+ private B2B SaaS companies, bootstrapped cohort). docus.ao outperforms at every stage due to Exponencial’s portfolio model — shared R&D, support, and G&A. By Y3-Y5, individual cost categories converge toward industry medians as dedicated allocation grows, but total spend remains well below the 95% median because portfolio sharing persists for G&A and infrastructure.

Portfolio Advantage vs. Standalone SaaS

Metric	Standalone Bootstrapped SaaS	docus.ao (Exponencial Portfolio)
Gross margin	75-85%	~90% (shared infra, small files)
Total spend (% of ARR)	95% (SaaS Capital 2025 median)	52-75% (shared resources)
Break-even timeline	18-24 months typical	~Month 6-8 (shared cost base)
First dedicated hire trigger	Day 1 (founder = hire)	~$200K ARR (Y3)
R&D cost at Y1	$50-100K (1-2 developers)	~$3K (marginal Exponencial hours)

When dedicated investment kicks in:

Trigger	Est. Timing	Investment	Why
Dedicated part-time sales	~$50K ARR (Y2)	~$8K/yr	Founder-led sales hits ceiling
Dedicated customer success	~$100K ARR (Y2-Y3)	~$15K/yr	Support tickets exceed shared capacity
Full-time R&D allocation	~$200K ARR (Y3)	~$40K/yr	Feature velocity requires dedicated attention
Dedicated marketing	~$300K ARR (Y4)	~$35K/yr	Content and campaign investment pays off
First non-Exponencial hire	~$500K ARR (Y5)	Market rate	Product revenue justifies standalone team

All estimates assume Angola labour market rates and Exponencial’s shared team model. Costs shift from “allocated shared hours” to “dedicated allocation” as ARR grows, not as step-function hires.

Key Milestones

Milestone	Target	Significance
First paying customer	Y1 Q1	Proof of concept
5 paying customers	Y1 Q2	Pilot validation
First customer with 100+ entities	Y1 Q3	Progressive pricing validated at scale
$50K ARR	Y2 Q3	Real business
100 customers	Y3 Q1	Scale beginning
First 500+ entity customer	Y2 Q4	Enterprise market validated
$500K ARR	Y5 Q1	Regional expansion ready

Infrastructure Cost Analysis

Why Hosting Costs Don’t Threaten Margins

A document management platform storing thousands of files might seem infrastructure-heavy. In practice, compliance documents (scanned PDFs, certificate photos) are small files, and cloud storage is commodity-priced. This section proves that infrastructure costs remain negligible at every stage of the 5-year projection.

Current Stack Costs

Service	Plan	Monthly Cost	What It Provides
Supabase	Pro	$25	PostgreSQL database (8 GB), file storage (100 GB), auth, edge functions
Cloudflare Pages	Free	$0	Frontend hosting, unlimited bandwidth, CDN, SSL
SMTP2Go	Starter	~$10	Transactional email (compliance alerts, invitations)
Kwenda (SMSPro)	Bulk packs	Variable	SMS alerts at $0.0114/SMS (Pacote Crescimento baseline)

Total fixed infrastructure: ~$35/month before any customers. SMS is pre-paid in bulk packs, not monthly — see VENDOR_COSTS.md for the full pack catalogue and planning baseline.

Document Storage Math

Average document sizes (validated against sample of 30 real documents from 5 companies — average 810.7 KB, range 105 KB to 1.2 MB):

Document Type	Typical Size	Examples
Text-based PDF	100-300 KB	AGT certificate, NIF certificate
Scanned certificate	300 KB - 1 MB	Alvara, INSS clearance, training cert
Phone photo of document	1-3 MB	ID photo, vehicle inspection slip
Multi-page scanned PDF	500 KB - 2 MB	Insurance policy, contract
Company presentation	5-10 MB	Designed PDFs with images

Three-layer storage model:

Company documents: 0.8 MB average (validated by sample data)
Entity documents (personnel/fleet): 1.5 MB average (scan-heavy IDs, certificates, photos)
Version multiplier: 2× (current version + 1 historical average)

Storage Per Customer Archetype

Customer	Entities	Company Docs	Entity Docs	With Versions	Total Storage
Small consulting (5)	5	40 × 0.8 MB	40 × 1.5 MB	× 2	~156 MB
Trading company (35)	35	40 × 0.8 MB	280 × 1.5 MB	× 2	~904 MB
Construction co (210)	210	40 × 0.8 MB	1,680 × 1.5 MB	× 2	~5.1 GB
Oil services (450)	450	40 × 0.8 MB	3,600 × 1.5 MB	× 2	~10.9 GB
Banco BIC (3,020)	3,020	40 × 0.8 MB	24,160 × 1.5 MB	× 2	~72.7 GB

Total Platform Storage by Year

All customers share a single Supabase project (multi-tenant).

Year	Customers	Total Storage	Supabase Overage Cost	ARR	Infra %
Y1	18	~7.5 GB	$0	$14K	3.4%
Y2	86	~50 GB	$0	$73K	1.5%
Y3	215	~178 GB	$1.64/mo	$200K	1.2%
Y4	450	~404 GB	$6.38/mo	$420K	1.4%
Y5	825	~756 GB	$13.78/mo	$780K	1.3%

Supabase Pro includes 100 GB of file storage. We stay comfortably within limits through Y2. Overage costs remain under $14/month even at Y5 with 825 customers.

Per-Entity Storage Economics

100 docs × 1.5 MB = 150 MB worst case per entity. At $0.021/GB: $0.003/month per entity in storage cost. Even the $0.70/entity rate at the highest tier is over 200× the marginal storage cost.

The Real Scaling Cost: Compute, Not Storage

Storage is essentially free. The actual constraint is database compute — CPU and RAM for handling concurrent queries as the customer base grows:

Year	Customers	Est. Concurrent Sessions	Compute Needed	Add-on Cost
Y1	18	10-30	Included (2 CPU, 1 GB RAM)	$0/mo
Y2	86	50-120	Included or Small	$0-25/mo
Y3	215	100-300	Small (2 CPU, 2 GB RAM)	~$25/mo
Y4	450	250-600	Medium (2 CPU, 4 GB RAM)	~$50/mo
Y5	825	500-1,500	Large (4 CPU, 8 GB RAM)	~$100/mo

Full Infrastructure Cost Projection

Year	ARR	Supabase Pro	Compute	Storage/Egress	SMTP2Go	Kwenda (SMSPro)	Cloudflare	Total Infra/yr	% of ARR
Y1	$14K	$300	$0	$0	$120	$70	$0	$490	3.5%
Y2	$73K	$300	$150	$0	$300	$480	$0	$1,230	1.7%
Y3	$200K	$300	$300	$0	$600	$1,200	$0	$2,400	1.2%
Y4	$420K	$300	$600	$120	$1,200	$3,400	$0	$5,620	1.3%
Y5	$780K	$300	$1,200	$400	$2,400	$5,800	$0	$10,100	1.3%

Infrastructure costs stay at 1-4% of ARR across the entire 5-year projection. Typical SaaS infrastructure costs are 5-15% of ARR, making docus.ao exceptionally efficient.

SMS cost by year assumes scale-appropriate pack size: Y1–Y2 on Pacote Crescimento ($0.0114/SMS); Y3 on Profissional ($0.0097); Y4 on Empresarial ($0.0091); Y5 on Escala ($0.0086). See VENDOR_COSTS.md for the full pack catalogue. As volume grows, COGS per SMS drops — a natural margin tailwind.

Why This Works

Documents are small files. Compliance certificates and scanned IDs are 0.5-1 MB, not videos or CAD files. A thousand documents fit in 500 MB.
Cloud storage is commodity-priced. $0.021/GB means 1 TB costs $21/month.
Multi-tenant efficiency. All customers share one Supabase project — no per-tenant infrastructure overhead.
Cloudflare Pages is free. Unlimited frontend bandwidth at zero cost.
SMS is the largest variable cost, not hosting — and it’s still <1% of revenue.
Per-entity storage cost ($0.003/mo) is over 200× below the lowest entity rate ($0.70).

When Would We Outgrow Supabase Pro?

Threshold	Trigger	Solution	Cost Impact
~500 concurrent users	Y3-Y4	Compute upgrade (Medium/Large)	+$50-100/mo
100 GB storage	Y4-Y5	Automatic overage billing	+$1-10/mo
~2,000 concurrent users	Post-Y5	Supabase Team plan ($599/mo)	+$574/mo
~5,000+ customers	Well post-Y5	Evaluate dedicated PostgreSQL	Revenue would be $3M+

Conclusion: Supabase Pro handles the entire 5-year projection. At the point where we’d consider alternatives (5,000+ customers), ARR would be $3M+ and infrastructure costs would still be <2% of revenue. The pricing model’s margins are safe at every projected scale.

LLM Feedback Synthesis

Insights gathered from Claude, ChatGPT, and Gemini analysis (December 2024):

Consensus Points (All Three Agreed)

The pain point is real and recurring
“Single-purpose compliance layer” positioning is strong
B2B SaaS subscription is the right model
Sticky product once documents are uploaded
Partner channels (accountants, lawyers) are key distribution
Trust/security is a critical barrier to address

Unique Insights by Source

Claude:

Mobile-first matters more than desktop in Angola market
“Excel is free” is harder to beat than it sounds - need failure stories
The only real validation: can you get 5 companies to pay in 60 days?

ChatGPT:

Onboarding/services revenue is realistic early, shrinks as product matures
“Network effect” potential if you become compliance handshake between companies
Distribution is the hardest part - product can be great but still slow without channel

Gemini:

“Reactive Panic → Proactive Readiness” is the core transformation to sell
OCR is not just “cool tech” - it’s essential for adoption
Subcontractor mandate angle: large companies require vendors to use docus.ao

Roadmap: Offline Mode

For field operations (logistics, construction sites):

Cache critical documents on device
“Show your Alvará when stopped by police in a dead zone”
Sync when back online

Priority: Post-pilot, based on customer demand Vertical fit: Logistics, Fleet, Construction

References

Product Requirements: docs/PRD.md
Technical Architecture: docs/TECH_PLAN.md
Domain Model: docs/architecture/DOMAIN_MODEL.md
Product Scope: docs/architecture/PRODUCT_SCOPE.md