How it works
A clear process, with your approval before anything is charged.
Here is every step from your first brief to code handover, including what happens after launch.
The process
Eleven steps, no surprises.
Scope is always approved in writing before paid project activation.
- 1
Select a plan
Choose a plan and a billing interval. The plan sets your commitment and change-request allowance. These are your starting preferences; nothing is charged at this point and you can change them during review.
- 2
Submit your brief
Describe what you need, who will use it, which platforms matter, and any integrations.
- 3
Review and discovery call
We review your brief first. If it is a good fit, we email you a link to book a short discovery call so we can ask questions and understand your business.
- 4
Fit review
We check that the project fits the plan you picked. If it is larger, we propose a published plan that fits or a smaller first scope. We never quietly change the price.
- 5
Approve the scope
You receive a versioned written scope: deliverables, exclusions, price, setup fee, and schedule. Once you accept it, we issue an initial invoice: the setup fee plus any approved one-time items (on Essential, also the 3 months paid upfront, or the first year on yearly billing). You pay it with PayPal in your customer portal, and the build starts once it is paid.
- 6
Design
We design the screens and flows around your requirements and share them with you for feedback before development starts.
- 7
Development
We build the agreed scope. You can follow progress through milestones, and preview links are shared as work becomes reviewable.
- 8
Review
You test the software against the agreed deliverables and tell us what needs adjusting before launch.
- 9
Deployment
Your subscription starts at launch, and we go live only after the first month's payment (or the first year's, on yearly billing). On Essential, the months you paid upfront cover the start, so the first subscription payment is taken when they end. We deploy to the hosting included in your plan, set up monitoring and backups, and help you publish to app stores where relevant.
- 10
Ongoing improvements
After launch, PayPal takes payment automatically on the same day each month (or year) as your first payment. You send change requests within your plan's allowance, one at a time. Each request is estimated and approved by you before it uses your allowance.
- 11
Code handover
When your commitment is complete and required payments are made, we deliver the agreed source code and documentation.
Billing and commitment
Pay monthly or annually. Stop any time.
The contract is month to month*. The commitment only decides when the code becomes yours.
On Essential, the first payment covers the setup fee and 3 months upfront. After that you can stop any time.
Billing interval
How often you are charged: monthly or annually. Annual is 12 times the monthly price. On Essential, the first payment covers the setup fee and 3 months upfront, then $35 a month.
Commitment period
How long you stay subscribed before you own the code, set by your plan: Essential and Growth 12 months, Business 24 months, Scale 36 months. It is not a minimum spend: you can stop earlier.
If you stop before the commitment is complete, your data is still yours: on request we export it in a convenient format that suits the data. The source code and database become yours once the commitment is complete. Cancellation takes effect at the end of the period you have already paid for.
After launch
Requesting improvements
Each plan includes change requests after delivery: Essential 2 per year, Growth 1 per month, Business 2 per month, Scale 3 per month, handled one at a time. Every request is estimated first; nothing uses your allowance until you approve the estimate, and any chargeable overage needs your explicit approval.
- New feature
- Something the software does not do yet.
- Content change
- Updating text, images, or other content.
- Bug
- Delivered functionality not working as agreed. Covered fixes do not reduce your feature allowance.
- Maintenance
- Updates, upgrades, and technical upkeep.
- Hosting change
- More capacity, storage, or a different supported region.
- Integration
- Connecting a new third-party service, priced per integration.
Request lifecycle
- 1Submitted
- 2Needs clarification
- 3Estimated
- 4Awaiting approval
- 5Queued
- 6In progress
- 7Ready for review
- 8Completed
Requests can also be declined, for example when they fall outside the service. We explain why.
Handover
When your commitment ends, the code and database are yours.
Handover requires a completed commitment and all required payments. After that you are free to keep running the application with us at the same rate or to move it elsewhere; handover does not cancel hosting or maintenance unless you choose to.
- Agreed source code
- Build and deployment instructions
- Dependency manifest
- Database schema and data export
- Configuration examples, without secrets
- Architecture notes and licence information
Credentials are transferred through a secure channel. Third-party software and services remain owned by their providers under their own licences.
More questions answeredTell us what you need built.
Share a short brief. Our team reviews it and gets back to you, and you get a written scope and price before you pay anything.