The long answers.

Anything digital: mobile apps, marketing sites, complex financial platforms, internal tools. Most of our work is for products where money moves, because that is where most of ours has gone. If we are not the right fit, we will say so on the first call and point you somewhere better.

Both. First-time founders shipping an MVP, and established teams modernising a system that has outgrown itself. The second is more common. Rebuilding around software that already exists, and that people depend on daily, is a different job from starting clean, and it is the one we are better at.

Small, and senior. You talk to the people building your product, not to an account manager who relays it. That caps how much we can take on at once, which is why we sometimes say we cannot start until a date rather than saying yes and staffing it thinly.

No fixed floor, but below a certain size the overhead of scoping and handover costs you more than it saves. An accessibility audit is the smallest fixed piece we sell. For anything under that, a short paid advisory session is often the honest answer.

English and Turkish, from London and Istanbul. The same people work across both studios, so you are not passed between them depending on where you are.

One discovery call, then a fixed proposal: scope, timeline, cost. We would rather take the time to understand the problem and quote a number we can stand behind than give you a range on the call and revise it upwards later.

It usually does. Small changes we absorb. Anything that moves the date or the number gets written down as a change, priced, and agreed before we build it. You will never open an invoice and find work on it you did not ask for.

Staged against delivery, not against the calendar. A deposit to start, then payments as agreed milestones land. Ongoing support and maintenance is billed monthly. We agree the currency and the payment terms with you before the first invoice.

You do, in full, once the final invoice is paid. That includes the source, the design files, the component library and the infrastructure configuration. We keep no licence over it and nothing is held back as leverage.

Good on work we have done before, honest about work we have not. A proposal marks the risky parts as risky rather than averaging them into a single confident figure. Where something genuinely cannot be estimated until it is investigated, we scope the investigation first and price the rest afterwards.

Short cycles. You see working software early and often rather than a demo at the end. Expect a regular call, a shared board you can read whenever you like, and a build you can click through as it grows.

It depends on what is being built and on how much of it already exists. A marketing site and a platform carrying integrations, compliance requirements and a migration are not the same job, and we will not pretend otherwise on a first call. The proposal gives you dates rather than a range, and you hear about a date at risk when we do, not on the day it slips.

Less than most people expect: a regular call, plus reviewing what we send between them. Discovery is the heavier part, and it is front-loaded. If you have no time at all to give it, say so early and we will structure the project to need less of you, which does cost more.

We stick around. Most clients keep us on a monthly retainer covering updates, dependency upgrades, store releases and an agreed response time when something breaks. Software nobody maintains does not hold still, it degrades somewhere you are not looking.

Yes, and some do. We write the code expecting that, and hand over the repository, the deployment pipeline, the environment setup and the documentation to run it. We will spend time with your team during the transition rather than posting a link and disappearing.

Often, yes. Most of our platform work starts with code we did not write. We will read it properly before quoting on it, and if the honest answer is that fixing it costs more than replacing it, that is the answer you get.

We design security in from the start rather than reviewing it at the end. We will sign an NDA before the first call if you would like, and your work stays private unless you tell us otherwise. Access to your systems is scoped to what the work needs and removed when it ends.

Wherever your obligations require, and we will ask about those before choosing anything. UK and EU regions are the default for clients with GDPR exposure. We do not move production data onto our own machines to debug with, and test environments run on generated or masked data.

Yes. Payments, lending and trading tools, built to survive audit and penetration testing. What that takes is on every project, audited or not: logging you can reconstruct an incident from, deployments you can roll back, and changes you can trace to a decision.

WCAG 2.2 AA is the standard we hold our own work to, this site included. We also audit other people’s products against it and against EN 301 549 for European Accessibility Act obligations, and hand the findings over as code changes a developer can act on.