Pricing/06Digital products and platforms
Digital products and platforms
Applications, portals, and tools — engineered as products.
Web applications, customer portals, dashboards, and internal tools. Priced per project because the honest answer depends entirely on the data model, the integrations, and how many edge cases the thing has to survive.
This is for you if
- You need software, not a website — logins, data, and state
- You have a workflow that off-the-shelf tools don't fit
- You're building a product, or a portal your customers log into
- You want a partner through several releases, not a one-off
Consider something else if
- A well-structured website would actually solve the problem
- An existing SaaS tool would do the job for a fraction of the cost
What you’reactually paying for.
Roughly how effort is distributed on a typical engagement at this tier. Illustrative of where the time goes — not a line-item invoice.
Discovery and architecture
20%Requirements, data modelling, and technical architecture — where most product risk is removed.
Product design
25%Flows, states, and interface design, including the empty, error, and edge cases.
Engineering
45%Application development, authentication, integrations, and admin tooling.
QA and launch
10%Testing, security review, deployment, and handover documentation.
Start tolaunch.
- Phase 1
Discovery and architecture
Requirements, user roles, data model, and technical approach — delivered as a written architecture you own, whether or not you continue with us.
- Phase 2
Design
Flows and interface design across the real states — loading, empty, error, and permission-denied included.
- Phase 3
Build
Development in reviewable increments, so you see working software early and often rather than at the end.
- Phase 4
Launch and iterate
Testing, deployment, documentation, and a plan for the releases after the first one.
Discovery
- Requirements and user roles
- Data modelling
- Technical architecture document
- Build estimate by phase
Design
- User flows
- Interface design across all states
- Design system for the product
- Responsive and accessible patterns
Engineering
- Application development
- Authentication and permissions
- Third-party and API integrations
- Admin tooling
Launch
- Testing and security review
- Deployment and environments
- Technical documentation
- Ongoing development capacity
What you provide
- A clear picture of the problem and who has it
- Access to subject-matter experts
- Decisions — product work stalls without them
- Any existing systems we need to integrate with
Not included
- Ongoing hosting and infrastructure costs
- Third-party API and service fees
- Support and SLA beyond the agreed term
- Marketing and go-to-market work
Why can't you give a price up front?
Because any number before discovery would be a guess. We can usually give a defensible range after one conversation, and a firm price after a paid discovery phase — which you own regardless of what you do next.
Can we start smaller?
Usually yes, and usually you should. A tightly scoped first release that real users touch beats a year-long build nobody has tested.
Who owns the code?
You do, on final payment. It's your repository, your infrastructure, and documented well enough that another team could pick it up.
Sound like theright fit?
Tell us about the business and we’ll confirm whether this is the tier you actually need — including when it isn’t.