Pick the shape that fits the problem
Most work falls into one of three shapes. If yours does not, say so on the call and you will get an honest answer about whether this is the right studio for it.
Web & SaaS applications
A working product on a real domain, with the boring parts done: accounts, roles, payments, email, backups, and a deploy pipeline anyone on your side can run.
Good fit for
- A first product for a funded startup
- A portal your customers log into
- Replacing a spreadsheet or an off-the-shelf tool that no longer fits
- Finishing a build someone else abandoned
You get
- The repository, in your organization
- Accounts and infrastructure in your name
- Tests and CI that block a bad deploy
- A written handover and a walkthrough call
- 30 days of support after launch
AI systems that behave
The distance between a convincing demo and something you can put in front of customers is evaluation, permissions and cost control. That distance is the work.
Good fit for
- Answering questions over your own documents
- Drafting, triage and classification inside an existing workflow
- Agent backends with real tools and real side effects
- A proof of concept that now has to be safe
You get
- An evaluation set built from your real cases
- Per-user permissions on what the model can read
- Tracing, so a bad answer can be explained
- Cost per request, measured rather than guessed
- A defined fallback for when the model is wrong
Embedded engineering
A set number of senior days each month inside your team. Useful when the work is real but the hiring is not worth it yet.
Good fit for
- A roadmap item nobody has capacity for
- A migration that keeps slipping
- Agencies needing overflow capacity, white-labelled
- A technical second opinion before a large commitment
You get
- Named days, booked in advance
- Work in your repository, your process, your tickets
- Pull requests your team reviews, not a delivered zip
- A monthly note on what changed and what is next
Scoping call
Thirty minutes. What you need, what it costs, and whether we are the right studio for it.
Fixed proposal
Scope, price and dates in writing within two business days. No hourly estimate that drifts.
Weekly builds
Something running on a real URL every week, so progress is visible rather than reported.
Handover
Your repository, your accounts, your deploys, and a walkthrough. Support afterwards if you want it.
The questions that come up on every call
- Who owns the code?
- You do, from the first commit. The repository lives in your organization and every account is created in your name.
- Fixed price or hourly?
- Projects are quoted fixed against a written scope, so the number does not move unless the scope does. Retainers are monthly. Hourly billing rewards slowness, so we avoid it.
- Why is there no pricing on the site?
- Because a number on a page is read as a quote, and what this costs depends on what you need. You get a fixed figure in writing within two business days of the call, before anything is built.
- What if the scope changes?
- It usually does. Changes are quoted as an addendum before any of it gets built, so nothing arrives as a surprise on an invoice.
- Who actually does the work?
- Yousef, on every project. When a specialist joins for part of it, you are told who and which part.
- Can you take over an existing codebase?
- Yes. That starts with a paid review first, quoted once we have seen the repository. You keep the written assessment whether or not we continue.
- Do you do design as well?
- Interface design, yes, and it is included. Brand identity and marketing sites we hand to people who do it better.
Still not sure which one you need?
That is what the call is for. Thirty minutes, no deck.