Pricing
A project is priced against the PRD you approve at the end of discovery. Operation after launch is a separate monthly engagement. Ask for a number and you get one by email.
Ask for a numberWhat you are paying for.
-
Week one
Discovery
A week with the people who own the problem. We write the feature request, the PRD and the design package, and agree what done means.
- Ends in a PRD and a design package you own
- You approve it before anything is built
- Comes with a price for the build
-
After approval
Build
Development in short cycles against the approved scope. Automated QA writes a report on every release candidate and a person reviews it before it ships.
- Priced per project against the PRD
- Changes are new feature requests, priced the same way
- Every document is yours as it is produced
-
After launch
Operate
We deploy it, monitor it and run releases, month to month. Production is where the next feature request comes from.
- Monthly, separate from the build
- Take it in-house whenever you are ready
- The record comes with it
Sydeso against the usual options
An honest look at how an engagement with us compares with a typical agency and with building in-house.
| Item | In-house | Typical agency | Sydeso |
|---|---|---|---|
| Who owns delivery | Your team, alongside everything else | The agency, until handover | Sydeso, through production and after |
| Where the record lives | Tickets, chat and documents | Status reports and a handover document | A written artifact for every stage, with a log of who approved what |
| How AI is used | Whatever each developer uses | Undisclosed, or a pitch | Agents do bounded work inside the process; a person reviews before anything ships |
| Who approves | Whoever is available | The agency PM | You, at two gates on every piece of work |
| After launch | Your on-call rotation | A support contract, if offered | We operate production and start the next run |
| Can you take it in-house later | It already is | Depends on the handover | Yes. You own the code, the accounts and every document |
| Price | Salaries and tooling | Day rates or fixed price | Per project, scoped at discovery |
Questions
- How is a project priced?
- Per project, against the scope written in the PRD at the end of discovery. Changes after that are new feature requests, scoped and priced the same way, so neither side is surprised by the invoice.
- What does discovery involve?
- A week with the people who own the problem. It ends with a PRD and a design package you own whether or not we build it, and a number for the build.
- Do you charge by the hour?
- No. Hours reward slow work. A price against an approved scope rewards shipping it.
- What does operation cost?
- A monthly engagement after launch that covers deployment, monitoring and releases. It is separate from the build, so you can take production in-house whenever you are ready.
- Do you take equity?
- No. Projects are priced in money against an approved scope.
- What happens if we stop?
- You keep everything: the code, the infrastructure accounts, the PRD, the design package, the QA and review reports. Nothing we build depends on our tooling.
Ask for a number.
Tell us the scope or the first feature. We reply by email with a price, not a call to book a call.
Ask for a number