Frequently Asked Questions

We design and build the technical infrastructure behind digital businesses — websites, web apps, mobile apps, AI automations, and the integrations that hold them together. Our work usually shows up under an agency's branding (white-label partnership) or directly for the brand owner who hired us.

Two groups. Digital agencies who hand off technical build work to us under their own name, and direct-to-consumer brand owners who need a build partner who understands the brand side of the work, not only the code.

Ahmedabad, India. We work with partners and brand owners across the United States, the United Kingdom, the Middle East, and Canada. Timezone coverage is handled through async handoffs and scheduled live windows.

Send us what you're working on through /start. Tell us what you're trying to build, what stage you're at, and what you need from a partner. We read every note ourselves. If there's a fit, we'll propose a short call to talk through the work.

The full sequence is on /process. Short version: we open with a problem fit conversation, write a working brief together, build in fortnightly rhythms with running visibility on what's done, ship with you in the room, then offer a Stays Program for the post-launch phase. Nothing about it is fixed-price-and-disappear.

It depends on what you're building and how much is already decided. Some engagements wrap in a few cycles, others run for multiple quarters. We map out the realistic shape during the working brief, before we ask you to commit to anything.

A focused sprint on one defined outcome. Useful when you want to test the relationship before committing to a full build.

Yes. Most partnerships open with a small piece of work (a fix, a feature, or a discovery sprint) so both sides see how the other operates before scaling up.

We talk about it before anything moves. New scope gets its own change note with the time, cost, and effect on the existing plan. You decide whether to bring it in, defer it, or trade something else out.

The realistic range is wide because the work is. A focused sprint sits at one end, a full multi-quarter build at the other. We give you a working number during the brief, not a stock pricing page that promises everyone the same answer.

Three operating modes. A fixed-scope project price, a retainer for ongoing partnerships, and an hourly mode for open-ended exploratory work. Every engagement gets the mode that matches its real shape.

No. The working brief is on us. We see it as part of figuring out whether we fit, not a billable phase.

Fixed-scope projects bill against milestones. Retainers bill monthly in advance. Hourly mode bills against a logged rate sheet you can see at any time. Invoices go out through standard cross-border channels.

Yes. A meaningful share of our work runs as a monthly retainer where we hold capacity for the partner's pipeline. Capacity, response shape, and pricing all live in a written partnership agreement before the first ticket lands.

Yes. Most of our engagements run under the partner agency's name. Your client sees you. The work product carries your branding. Our name doesn't appear on the deliverable unless we both agree otherwise.

Only if you tell them. Standard partnerships include a mutual NDA that keeps the relationship confidential. We don't reach out to your client. We don't pitch them. We don't end up on their vendor list.

We sign a mutual NDA at the start of any partnership. Custom NDAs from your firm or your client's legal team are fine. Send them over with your first message. We'll review and either sign or come back with a small set of clarifying edits.

Yes. The price you quote your client is your call. We give you our partner rate; what you charge on top of it sits between you and them.

Either model. The default is through you. We treat you as the operating contact, and your client never sees a message from us. If you'd rather have us join client calls or write under your domain, we can set that up too.

We do this often. We can join as your technical team, present scope and feasibility live, and stay quiet on commercials. Your call. Your contract. Your relationship.

Yes. Brand owners who don't have a build team in-house come to us to design and ship the technical side of the business. The engagement runs the same way as an agency partnership; the relationship is with you.

Both. The work we do most often blends them. A build that ignores the brand reads as cold and converts poorly. We treat brand decisions as load-bearing, not decoration.

Yes. We've inherited live builds in mid-flight more than once. The first thing we do is audit what's there, document what's holding the system up, and write a stabilisation plan before changing anything.

Next.js for the web layer, Sanity for content management, Postgres on Supabase for data, Resend for transactional email, Cal.com for scheduling, Vercel for hosting. We adjust the stack to fit what the project needs.

Yes. WordPress, Shopify, Webflow, custom React stacks, Laravel, Django. If there's a documented technology and a real reason to stay on it, we work in it. We'll flag where the existing stack is going to cost more than a careful migration.

Yes. Workflow automations, agent-style integrations, document processing, lead routing, internal tooling. We treat AI as a tool that earns its place by removing real friction, not as a marketing line.

You do. On full payment for the work, the code, the design, the content, and every asset built for you transfers to your name. Repository access, deployment credentials, and DNS sit with you from the start.

We can. Vercel handles the front-end layer on most builds. If you'd rather host elsewhere or stay on your existing infrastructure, we hand it over and document the deployment.

Yes. The post-launch phase is the Stays Program, a structured way of staying in the build after it ships. The next section covers it in detail.

Our post-launch operating model. It runs in three phases (Stabilize, Tune, Plan) followed by a maintenance tier the partner picks (Watch, Build, Grow). It's how we make sure a launched build keeps earning instead of slowly decaying.

No. You can take the build and run it on your own infrastructure once we hand it over. The Stays Program is offered because most builds that go silent at launch end up costing more to fix later than they would have to maintain steadily.

Yes. The maintenance tier is month-to-month after the initial structured phase. Cancel with one billing cycle of notice. We hand over the running playbook and the most recent state of the system.

The structured phase is priced per build. The maintenance tier has three pricing modes depending on which one you pick (Watch, Build, Grow). Both numbers land in the working brief before you sign.

Almost every partnership we run includes a mutual NDA. That covers the agency partner's brand identity, the end client's identity, the technical detail of the build, and the commercial terms. Putting that on a public case study would breach the agreement.

The full library lives at /nda-protected. Tell us you're evaluating us, send us your NDA (or sign ours), and we open up the case studies, technical write-ups, and build artefacts that don't sit on the public site.

Yes. Send it through. We'll review with our legal team and either counter-sign, or come back with a small set of clarifying edits where the language conflicts with how we operate.

A decision we've made until our first cohort of engagements are signed and live. We'd rather be judged on what shows up on a call and on a build than on a polished founder page. /about explains the reasoning in full.

A named build team led by one of the co-founders. Every engagement has one operating contact, one technical lead, and a small build team behind them. Nothing routes through an account manager who has no view on the work.

Small on purpose. Big enough to ship serious work, small enough that the people you talk to are the people on the build. We add team where the work warrants it, not because we're optimising for headcount on a website.

India Standard Time as the operating base. We hold scheduled live windows in your timezone (East Coast US, West Coast US, UK, Middle East) and run the rest async. Async is the load-bearing piece, most build progress lands while you sleep.

Same-day on weekdays for active partners. The exact response shape (live channels, escalation path, on-call window) sits in the partnership agreement so neither side guesses.

If the cause sits inside our build, we fix it under the warranty window or under the Stays Program if you're enrolled. If the cause sits in something we don't operate (your hosting, a third-party tool, a code path your team added), we still help, billed at the agreed hourly rate for that work.

The fortnightly rhythm gives both sides natural exit points. If the partnership is wrong, we close out the current cycle, hand over what's done, and you owe nothing for work that hasn't started.

On work that's been done, no, we deliver against milestones and hours that have already been invested. On work that hasn't started, yes, any pre-paid amount comes back to you without argument.

Bugs that come from our build are fixed at no cost during the post-launch warranty window. After that, it's covered by your Stays Program tier if you're enrolled, or billed hourly if you're not.