Questions
The things people ask before signing
If your question is not here, email us and we will answer it straight — including the ones with awkward answers.
Engagement
How do projects usually start?
With a paid two-week discovery sprint. We interview your team, audit any existing system and produce a costed technical roadmap. You own that document outright — a fair number of clients take it and build in-house, and that is a legitimate outcome.
What does a typical project cost?
Discovery sprints are fixed-price. Build engagements are priced per two-week sprint based on team composition, and most MVPs land between six and ten sprints. You get a full cost projection at the end of discovery, before committing to any build.
Can you work with our existing in-house team?
Yes, and it is common. We embed into your repository, your ticket tracker and your standups. Some engagements are a full delivery team, others are two specialists filling a specific gap for a quarter.
What happens when the project ends?
You get the repository, the infrastructure-as-code, the runbooks and a handover period with your own engineers. We also offer ongoing support retainers, but they are optional and month-to-month — never a condition of delivery.
Technical
Who owns the intellectual property?
You do, completely, from the first commit. Code is written directly into a repository you control, under your cloud account. There is no proprietary framework or licence that follows you afterwards.
How do you handle security and compliance?
Threat modelling happens during design, not after launch. We work to least-privilege access, encrypted data at rest and in transit, and dependency scanning in CI. For regulated sectors we have delivered against SOC 2, ISO 27001, HIPAA and GDPR requirements.
What is your testing and deployment approach?
Automated tests run on every pull request, and nothing merges without review and a green pipeline. Deployments go through staging first, and production releases are reversible — we would rather roll back in ninety seconds than debug under pressure.
Do you take on legacy systems?
Frequently, and rarely by full rewrite. We prefer incremental extraction: strangle the monolith service by service while it keeps serving traffic. It is slower on paper and far less likely to end in a failed migration.
Get in touch
Tell us what you are building
A short call, an honest read on whether we are the right fit, and a clear next step either way. No pitch deck.
Replies within one working day