Questions, answered plainly
Scope, cost, timelines, and what happens after launch. If something here is not covered, ask and you will get the same straight answer.
What does a typical project cost?
It depends on scope, but we quote a fixed price per phase rather than an open-ended hourly rate, so you know the number before work starts. Small marketing sites and MVPs usually run in weeks; multi-platform products with billing and roles run longer. You get the estimate broken down by phase, not as a single headline figure.
How long will it take?
A marketing site is typically two to four weeks. A mobile app with a backend is typically two to four months to first store release. We give you a phase-by-phase schedule up front and a working build every week, so slippage is visible immediately rather than at the end.
Do you work with existing codebases?
Yes. We take on rescue work, feature builds on top of someone else's code, and migrations. The first step is a short paid review so we can tell you honestly whether the existing code is worth extending or cheaper to replace.
Who owns the code and the accounts?
You do, from day one. Repositories, cloud projects, store listings, and domains are created in your name or transferred to you at handover. There is no lock-in and no license to buy back.
Will I talk to the people writing the code?
Yes. There is no account manager relaying requirements second-hand. You work directly with the designers and engineers on your project, which is why the studio stays small on purpose.
What happens after launch?
Launch is when real usage starts, so we offer ongoing support: OS and dependency upgrades, store resubmissions, monitoring, performance work, and someone to call when something breaks. It is a separate monthly arrangement, never a condition of the build.
Can you do just the design, or just the build?
Yes to both. Plenty of clients come with finished designs and need engineering, or need a design system their own developers will build from. We are happy to take either half.
Can I hire a developer from your team?
Yes. Our remote development services let you hire a developer directly from our team, matched to the skills, experience level, and project you need covered. You brief us once and we confirm who is available.
Can I hire a developer part-time?
Part-time engagement is available depending on the developer's current availability. Tell us the hours per week you need and we will confirm a part-time developer who fits, rather than requiring a full-time commitment.
Can I hire developers on a monthly basis?
Yes. Monthly hiring is our standard model for dedicated developers: the same person or a small remote development team stays on your project continuously, for as long as you need them, rather than a one-off fixed-scope contract.
What technologies are available?
Our remote development team covers React, Next.js, and Node.js on the web, React Native, Expo, and Flutter for mobile, MongoDB, PostgreSQL, and MySQL for data, and AI integrations. Tell us your stack and we will confirm who is available before you commit.
Can I interview the developer before hiring?
Yes. Share your requirements and we will introduce a suitable developer for a short interview before any engagement starts, so you know who you are hiring and how they work.
Can I increase or reduce the team later?
Yes. You can scale your remote development team up or down as project requirements change, adding or releasing developers without renegotiating the arrangement from scratch.
Do you build AI and LLM features?
Yes. We integrate large language models into web and mobile products: assistants and chat interfaces, retrieval-augmented generation (RAG) over your own documents, semantic search, summarisation, extraction, and classification. We build against the Anthropic Claude and OpenAI APIs, and we pick the model per task rather than defaulting to the largest one available.
Can you add AI to a product we already have?
Usually yes, and it is often the cheaper path. Most AI features are additive: a retrieval layer over your existing data, an endpoint your current front end calls, or an internal automation that uses the APIs you already have. We start with a short review of your data and stack, then scope the smallest useful version rather than a rewrite.
How do you keep AI costs and quality under control?
Both are engineering problems, not luck. On cost: right-sized models per task, prompt caching, batching where latency allows, and token budgets with monitoring so spend is visible before the invoice. On quality: an evaluation set built from your real cases, guardrails on what the model is allowed to do, and human review on anything irreversible. You get the numbers, not just a demo that worked once.
How do we start?
Send a short description of what you want to build through the contact form. We reply with questions, a rough scope, and an honest read on feasibility, usually within two working days. No commitment at that stage.
Contact usTell us what you want to build
Share the idea, the deadline, or just the problem. You will get a straight answer on scope and feasibility, not a sales sequence.
