Fixed scope. Fixed price.
Three ways to work with us. No hourly billing, no open-ended retainers you can't budget for. You know the cost before we start. We don't invoice until scope is agreed.
Pilot
One narrow build. The fastest way to see if working with us is worth a bigger commitment.
- One well-defined feature or tool
- A single data source or document type
- Working software, deployed and handed over
- Source code, fully yours
- Multi-system integrations
- Ongoing changes after handover (available separately)
- Open-ended discovery (the scope is fixed before we start)
MVP
A custom build: a full product, internal tool, or multi-step workflow, scoped to your actual requirements.
- A scoping call to define exact requirements and price within the band
- Multiple features or integrations, as agreed in scope
- Weekly builds you can test as we go
- Deployment, documentation, and handover
- Source code, fully yours
- Work outside the agreed scope (changes go through a clear change process, not silent scope creep)
Ongoing
For after launch: keep improving what we built, or add support hours for a system already in production.
- Monthly retainer, scoped to your actual usage
- Bug fixes and small iterations
- Priority response over one-off requests
What fits in a $2,000 Pilot
One narrow, well-defined build, not a full product. If it needs multiple systems, users, or document formats, it usually belongs in the MVP tier.
One document type → structured data
e.g. one invoice or statement template extracted to CSV/JSON, with a simple review step for low-confidence rows.
FAQ chatbot over a fixed set of docs
Answers only from a folder you provide (policies, manuals, SOPs), not the open web.
Inbound email or ticket triage
Label by topic or urgency and route to a shared inbox, sheet, or queue you already use.
Spec sheet → listing copy
Turn structured product data into consistent product descriptions for a catalog slice.
Spreadsheet export → written summary
A scheduled or on-demand summary report from one export format your team already produces.
One AI feature wired into an existing app
A single integration (one provider, one workflow), not a new product from scratch.
Not sure which tier fits yet?
That's normal. Plenty of teams know the problem long before they know the project. That's usually how we start anyway: we listen first, and the actual scope tends to fall out of that conversation rather than the other way around.
We won't invoice until scope is agreed.
Get a scoping conversationQuestions
What exactly do I get for $2,000?
One narrow, well-defined build: a single tool or feature working against a single data source. We agree the exact scope before any work starts, and it's fixed at that price. It's designed to be a fast, low-risk way to see how we work. See the Pilot examples above for typical shapes.
When do you invoice?
We don't invoice until scope is agreed. Once the deliverable, timeline, and price are written down and you approve them, that's when billing starts, not before.
What happens if the project needs more than we scoped?
We tell you before doing extra work, not after. If new requirements come up mid-project, we quote them separately as a change rather than quietly expanding the original price. Nothing gets added to your invoice without you agreeing to it first.
Who owns the code?
You do: full source code, no licensing fees back to us, no lock-in. Once a project ships, it belongs to you.
Where is your team based?
India: Navi Mumbai, specifically. We've been building software for 20 years. Being India-based is part of how we keep fixed prices this low without cutting corners on the work.
How fast can you start?
Usually within a few days of the scoping call, once the price and scope are agreed. Pilot projects can often start the same week.
What if I don't know exactly what I need yet?
That's normal, and it's what the scoping call is for. Come with a rough problem, not a finished spec, and we'll help turn it into something concrete enough to price and build.
What tech stack do you use?
Whatever fits the product and your team's ability to maintain it afterward, usually a standard web stack with an AI layer on top. We pick tools for reliability, not novelty. Common providers include OpenAI, Azure OpenAI, and Anthropic.
Do you work with US and EU clients? What about time zones?
Yes. We're based in India (IST) and work with clients worldwide. Scoping calls are scheduled to overlap with your hours; async updates and weekly demos keep the build moving without requiring same-timezone standups.
What do you need from me to start?
A rough problem statement, access or samples for the data or documents involved (once scope is agreed), and one decision-maker for scope and feedback. We lock deliverable, timeline, and price in writing before invoicing.
How does this compare to DIY ChatGPT, a freelancer, or a big agency?
DIY and freelancers can get a demo working; production tools need ownership, handover, and something that still works in six months. Big agencies often start at enterprise budgets and long timelines. We're fixed-scope builds for small teams: from $2,000, in weeks, with source code you own.