For mobile app agencies
An app proposal has to survive a founder, a CTO and an app store reviewer.
Agency app projects are usually sold in two steps: a paid discovery or scoping phase, then a build quote. The build quote is read by a founder who wants features, a technical adviser who wants architecture, and sometimes an investor who wants a date. Then the app store rejects the first submission, a third-party API changes its pricing, and the client wants an Android version 'since it's the same code'.
ApeiroCraft lets your team send the build as a phased proposal with platforms, exclusions, third-party costs, store submission and handover spelled out. You see when it's opened and reopened, it's signed in the browser, and each phase is invoiced from the accepted proposal. Pricing is flat per account: Team is $79/month for up to 5 people; Agency is $149/month for up to 20.
Where app projects slip.
'Same code, both platforms'
The client assumed iOS and Android, phone and tablet, and a web admin panel. The proposal said 'mobile app'.
Third-party surprises
Maps, SMS, payments, push notifications, analytics: each has its own pricing, terms and quirks. If the proposal didn't separate them, they become your cost or your fault.
Store review and launch dates
A rejection from app review pushes launch by a week. If the proposal promised a date without that caveat, it reads as a missed deadline.
Discovery to handover, phase by phase.
Platforms and phases, explicit
List platforms, devices and the admin side in scope, then each phase with deliverables and an exit point — so the client can stop after the MVP without a dispute.
See it circulate before the board meeting
Opens and re-opens are recorded on the link. A spike of opens the day before a client's investor update tells your account lead when to call.
One signed SOW
The signature records name, email, IP address and a UTC timestamp and can't be changed afterwards — the exclusions list is on record.
Phase invoices, team-wide
Convert the accepted proposal to a draft invoice for discovery or the first phase. Convert again at each phase. Your whole team works from the same client record and pipeline.
What a mobile app proposal has to include.
Write the exclusions list before the price. In app work, it's what the client reads twice.
Platforms and devices
If it's left vague
Android, tablets and a web admin are assumed to be included.
With ApeiroCraft
Name platforms, minimum OS versions, device classes and any admin panel.
Features and exclusions
If it's left vague
Features mentioned in discovery calls drift into the build.
With ApeiroCraft
List features in scope per phase and an explicit list of what's excluded.
Third-party services
If it's left vague
API and service fees end up on your invoice or in a dispute.
With ApeiroCraft
List each service, that its fees are the client's, and that changes to its terms may affect scope.
App store submission
If it's left vague
A rejection is treated as a missed deadline.
With ApeiroCraft
Say who owns the developer accounts, that review timing isn't in your control, and how resubmissions are handled.
Acceptance, warranty and handover
If it's left vague
Bug fixes continue for months, and the client wants the source on day one.
With ApeiroCraft
Define acceptance testing, a warranty period for defects, and when code and accounts are handed over.
- Agency is $149/month flat for up to 20 people, not per seat.
- Shared pipeline, tasks and notes for account and delivery leads.
- Phase invoices in the client's currency, set per invoice.
Common questions.
How do app agencies usually price projects?
Common models are a fixed-fee discovery phase followed by a fixed-price build per phase, time-and-materials with a monthly cap, or a dedicated team on a monthly rate. Post-launch support is usually a retainer. ApeiroCraft holds the model you use and invoices it; it doesn't estimate effort.
What does an MVP build proposal look like?
A summary of discovery; iOS and Android phone apps from one codebase plus a basic web admin; phase one with sign-up, profiles and the core booking flow; phase two with payments and notifications; exclusions including tablet layouts and offline mode; third-party services listed as client-paid; app store submission from the client's developer accounts; a defect warranty after acceptance; payment per phase. The founder reopens it before an investor call, signs, and your account lead invoices phase one.
When is ApeiroCraft not the right fit for an app agency?
It isn't delivery tooling: there's no sprint planning, issue tracker, time tracking or resource planning, and no API to sync with them. Agencies billing time-and-materials from timesheets need a time tracker alongside. ApeiroCraft fits the sales and billing side — proposals, signatures, pipeline and phase invoices.
Can several people on our team work on a proposal?
Yes. Everyone in the workspace can work from the same pipeline, client records, notes and tasks. The plan sets how many people: Solo up to 3, Team 5, Agency 20.
Which template should we use?
The app development template: scope with an exclusions list, phased gates you can stop at, acceptance criteria and IP handover.
Put the exclusions list above the price.
Start from the app development template and send your next phased SOW.
Start freeStill deciding? Talk to the founder
Keep reading
Free template
App development proposal template
Scope with an explicit exclusions list, phased gates, acceptance criteria, and IP handover.
Solution
ApeiroCraft for agencies & studios
Shared pipeline, contractor roles, flat workspace pricing rather than a charge per person.
Guide
Flat-rate vs per-seat proposal software
The real arithmetic for a 3, 5, and 8-person team across seven tools.