Engagement models

Three paths into a working product. The form picks the right one for you.

On Day 1, where you are matters more than what your engagement is called. Some founders need a registered company and a payment gateway just to take a first dollar. Others already run their own ops and just need code shipped. We named three archetypes to make that decision visible — but you don't have to pick the right one. Start a request, describe where you are, and we route you to the path that fits.

Start a BOT request Read about BOT in detail

How to read this page

Each path is a real engagement we've shipped or are shipping.

Below: who each model is for, what we build during Build, how we operate (or hand off) during Operate, and what transfers — code, accounts, brand, IP, ownership — at the end. The shape of the commercials is described in plain English; the specific figures (build fee, equity, profit split, retainer rate) are agreed during scoping and written into the master service agreement before any work starts. There are no hidden fees and no surprise invoices, ever.

BOT

Build-Operate-Transfer

For founders with an idea but no business or gateway yet

You have a validated idea, often some early customer signal, and time. You don't yet have a registered company, a payment gateway, a cloud account, or an engineering team. We launch under our infrastructure and hand it back to you when you're ready.

Owns at end

You own everything: code, IP, brand, customers, cash.

Shape of commercials

A milestone-based build fee during Build, a monthly operating retainer during Operate, and a one-time transfer assistance fee at handover. All three are agreed up front during scoping and written into the MSA.

Specific figures (build fee, retainer rate, equity, profit split) are agreed during scoping and written into the master service agreement before any work starts.

Best when

You haven't incorporated yet, or your entity isn't ready to take payments.
You want to validate the market before committing to a full company setup.
You'd rather pay for a runway than for the overhead of hiring engineers and ops staff.
You expect to take the product back into your own hands once it has traction.

Not for you if

You already have a registered company and want to launch under your own brand on day one — see Build + Transfer.

What we build

Production-ready v1, scoped tightly during a paid scoping call.
Two-week sprints, senior engineers only, demo at the end of each sprint.
Brand identity, marketing site, and app under the Ganakys legal vehicle.

How we operate

We host on our cloud accounts, monitor 24×7, patch dependencies, and ship improvements monthly.
Payments flow through our Razorpay merchant account; revenue lands in a project-specific ledger you can see live in the client portal.
Monthly operating report: bookings, MRR, infrastructure cost, support load, support backlog.

Transfer / exit shape

Code repository, container images, cloud accounts, domain, brand, and customer database transfer to your name.
Customer-of-record on the payment gateway moves to your entity once you've registered and KYC'd.
Transfer happens within 30 days of trigger — you ask, we hand over.

Start a request with BOT pre-selected Or talk to us first

B+T

Build + Transfer

For teams that already run their own ops

You already have a registered business, a payment gateway, and the team to run a product on Day 1. We build, you launch under your own name, and we hand over at production-ready.

Owns at end

You own everything from day one — we never hold infrastructure, accounts, or IP under our name.

Shape of commercials

A milestone-based build fee, paid in three or four tranches tied to scoping → design freeze → beta → production. No ongoing fees after delivery.

Specific figures (build fee, retainer rate, equity, profit split) are agreed during scoping and written into the master service agreement before any work starts.

Best when

You're an existing business adding a software product.
You have your own DevOps/SRE team or comfortable using a managed cloud.
You want senior engineering on the build but no long-term operating dependency.

Not for you if

You don't have a payment gateway, cloud team, or registered entity — see BOT.
You want us to keep operating the product after launch — see Build + Operate-as-a-Service.

What we build

Production-ready v1 inside your cloud accounts and your code repos from day one.
Senior engineers pair with your team during Build; we leave behind documentation, runbooks, and a handover walkthrough.
Your brand, your domain, your payment gateway end-to-end.

Operate (none — direct handover)

There is no Operate phase. The product launches under your name and your operations the day Build ends.
We offer a 30-day post-launch warranty — bugs introduced during Build are fixed at no extra cost.

Transfer / exit shape

Final commit, runbook handover, and a 60-minute walkthrough with your engineering lead. That's the entire transfer.
Optional retainer for warranty extension or post-launch enhancements, billed separately.

Start a request with B+T pre-selected Or talk to us first

B+OaaS

Build + Operate-as-a-Service

For owners who want the build done and the ops outsourced

Your company is set up but you'd rather pay us to keep the lights on than hire and manage an internal team. We build, then run it for you on a monthly retainer.

Owns at end

You own the product, the IP, the customers, the cloud accounts. We rent you the engineering hands.

Shape of commercials

A milestone-based build fee, then a monthly retainer scoped against agreed SLAs and on-call hours. Infrastructure cost is passed through at cost. Retainer is reviewed annually.

Specific figures (build fee, retainer rate, equity, profit split) are agreed during scoping and written into the master service agreement before any work starts.

Best when

You own the product and the customer relationship, but you don't want an in-house engineering or DevOps team.
You want predictable monthly cost rather than capex on hiring.
You may eventually want to bring operations in-house — and you want a clean off-ramp when that day comes.

Not for you if

You want a one-shot delivery and to own ops from day one — see Build + Transfer.
You haven't incorporated and need us to carry the legal vehicle — see BOT.

What we build

Production-ready v1 inside your cloud accounts, your repos, your brand.
Operations-ready: alerting, on-call rotation, runbooks, deploy automation, dependency-update cadence.

How we operate

We run hosting, on-call, monitoring, dependency upgrades, security patching, and incident response on a monthly retainer.
Monthly operating report: uptime, incidents, performance, infrastructure cost (passed through at cost + agreed margin), feature backlog.
Roadmap reviewed quarterly with you. You set priorities; we ship them.

Transfer / exit shape

30-day notice, either side. We hand over runbooks, on-call rotation, and infrastructure access. Cleanly.
Optional knowledge-transfer engagement to onboard your in-house team if you decide to bring ops back home.

Start a request with B+OaaS pre-selected Or talk to us first

At a glance

All three at a glance

If you're trying to figure out which model fits, this is the skim view. If you're not sure, the form below picks for you.

Model	Carries the legal vehicle?	Carries the payment gateway?	Operates after launch?	Who owns at end?
BOTBuild-Operate-Transfer	Yes (during Operate)	Yes (during Operate)	Yes — until transfer	Founder
B+TBuild + Transfer	No	No	No	Founder
B+OaaSBuild + Operate-as-a-Service	No	No	Yes — on retainer	Founder

Still not sure which one fits?

Tell us about your idea — we'll route you.

Submit a short BOT request describing where you are and what you want to build. The intake form has a soft preference for the engagement model; if you leave it blank, we pick during scoping. There's no commitment to any specific path until the MSA is signed.

Start a BOT request Talk to us first