Clear scope, clear starting points
Pricing that gives the idea somewhere to start.
Every build is different, but the way we work is not. Choose a starting point, then we will shape the scope around the product, platform, people, and release needs it has to serve.
Build in the right lane.
These are starting points, not artificial packages. Final scope depends on features, integrations, platforms, content, and release requirements.
Starter
A focused first release
- One focused product or workflow
- Core screens and functionality
- Clear handoff and documentation
- 1 month of support
- 2 revision rounds
Professional
A production-ready product
- Polished app, plugin, extension, or site
- Database and API integration
- Responsive product experience
- 3 months of support
- Release guidance and QA
Custom product
A bigger idea, properly shaped
- Multi-platform or advanced build
- AI, automation, or complex integrations
- Cloud or local deployment planning
- Priority support
- Long-term product roadmap
All prices are starting points shown in USD by default. The website can display the visitor’s local currency automatically where supported.
What changes the estimate?
The number is shaped by the work behind the interface. These are the conversations that make a quote useful.
Product depth
A small focused workflow is different from a product with roles, settings, history, and multiple user journeys.
Platform count
Windows, iOS, Mac, web, WordPress, and browser builds each have their own release and testing needs.
Integrations
Existing APIs, payments, authentication, AI providers, files, and third-party services add real planning work.
Content and migration
Moving data, writing content, preparing listings, or rebuilding an existing experience affects the first release.
Privacy and deployment
Offline use, private infrastructure, permissions, security, and operational ownership deserve early attention.
Support horizon
Launch assistance, maintenance, new features, and ongoing optimisation can be planned from the beginning.
What is included in a healthy project?
A credible engagement is more than a handover of code. It creates enough understanding for the work to be useful after release.
| Stage | What happens | What you can expect |
|---|---|---|
| Discovery | Clarify users, workflow, scope, risks, and outcome. | A brief that gives the build a reason and a boundary. |
| Design | Shape the key flow, visual direction, states, and content structure. | Something tangible to review before the full build. |
| Development | Implement, integrate, test, and refine in visible increments. | Working progress with decisions explained clearly. |
| Launch | Prepare release, documentation, analytics, and support path. | A product your team can operate and improve. |
Choose a platform, or connect several.
Our service pages explain the kind of work each path involves. The right first platform depends on the audience and the moment you want to improve.
Questions before you request a quote.
We would rather make the first conversation useful than pretend every project can be priced from one sentence.
Can you work with a small initial budget?
Yes. We can narrow the first release around the most valuable workflow and identify what can wait until there is evidence.
Do you quote fixed-price projects?
Where the scope is clear, yes. For larger or exploratory work, staged milestones can create a fairer way to manage uncertainty.
Can you continue after launch?
Yes. Support, maintenance, content, product improvements, and new platform releases can be planned as an ongoing relationship.
What should I send to start?
Tell us who the product is for, what is difficult today, and what a better outcome would look like. A rough note is enough.
Want a number that relates to your actual product?
Send the rough version. We will ask the questions that make the estimate more useful.