ONE
Paid discovery, yours to keep
The specification works with any developer. It is not a sales document dressed up as a deliverable.
We are a small development team in Dubai Silicon Oasis. We build the projects that a page builder cannot carry, and we are unusually direct about which projects those are not.
How we estimate
Discovery is paid, short and separate. One or two weeks that end in a written specification, a tested prototype of whatever integration looks risky, and a number. The specification belongs to you: take it to another developer and it still works.
After that the price is fixed against that scope. Changes are quoted before they are built. Nobody discovers a new line on the final invoice, because you approved every one of them on the way.
Why we spike integrations first
Development projects rarely overrun because the code was hard. They overrun because an external system behaved differently from its documentation, and nobody found out until week six.
So we test the risky connection in a throwaway prototype before quoting the work around it. An hour spent there regularly saves a month, and occasionally it changes the recommendation entirely.
What you own at the end
- The repository, in your organisation, with readable commit history
- Hosting, domain and DNS in accounts registered to you
- Every third-party account, from the CMS to the error tracker
- The deployment pipeline and environment configuration
- Documentation, plus a recorded walkthrough for whoever inherits it
There is no layer only we understand and nothing we can switch off. If you bring the work in-house next year, that should be an ordinary handover rather than a rescue project.
Work we turn down
Fixed deadlines attached to unfixed scope. Projects where we would be the third team and nobody will discuss what happened to the first two. Applications where the budget covers the build but not the year of support that a live system inevitably needs.
We would rather lose the work than take it on terms where it cannot succeed, which is why the scoping conversation is free and reasonably long.
Four things we hold to
TWO
Risk tested before pricing
We prototype the uncertain integration first. Estimating around an untested system is guessing with your money.
THREE
Working software every fortnight
On a staging URL you can open. Nothing is revealed for the first time at the end.
FOUR
Handover as a default
Every project is built so somebody else could take it over. That is a feature, not a risk to us.
The practice is the engineering side of Dubyte AI Solutions. The AI systems and internal tools these applications often talk to are built by the same team, on the main studio site.
Tell us what it has to do
Send the requirement, however roughly it is written. You get back the questions we would need answered, the integrations we would test first, and a realistic range.