How we work
Understand the problem. Prove it small. Build it properly.
Every engagement follows the same four stages, whatever we are building. Each stage ends with something you can use, and a decision point where you can stop.
Discovery
A short, fixed-fee phase. We map the workflow, the data and the systems involved, agree the numbers that define success, and write a plan with a scope and estimate for the first build. The plan is yours whether or not you continue with us.
Prototype
A narrow, working version on your real data, usually within weeks. It is tested against real cases before anyone decides to scale it, so the decision to continue is made on evidence.
Build
Production engineering: security, permissions, integrations, monitoring and documentation, delivered in slices with a demo every two weeks. Well-defined scopes are fixed price; evolving products run milestone by milestone with an agreed monthly cap.
Operate and improve
We measure real usage, fix what the data shows and extend what works. Support continues on terms that fit your team, or we hand over cleanly to your engineers.
What you own
Everything we build for you.
You own everything we build for you: source code, infrastructure, documentation and data. What Genesis keeps is general engineering know-how and internal tooling that contains none of your code or data. If we ever want to reuse something specific, we ask first and put it in writing.
After you write
What happens next
- A reply by email, usually with a few clarifying questions.
- A short call to understand the problem and the systems involved.
- A proposed first step, normally a fixed-fee discovery phase. If we are not the right fit we will say so and, where we can, point you somewhere better.
Common questions
How does an engagement start?
With discovery: a fixed-fee phase where we map the workflow, the data and the systems involved, agree the metrics that matter, and propose a scoped plan with milestones and a budget.
Do you take fixed-price projects?
For well-defined scopes, yes. For products that will evolve, we recommend discovery followed by milestone-based delivery with an agreed monthly cap.
Who owns the code and the data?
You own everything we build for you: source code, infrastructure, documentation and data. What Genesis keeps is general engineering know-how and internal tooling that contains none of your code or data. If we ever want to reuse something specific, we ask first and put it in writing.
Do you work with small and mid-sized businesses?
Yes. Much of the highest-return automation and AI work is in growing businesses, where a few well-built systems change how the whole team operates.
Can you work with our existing team?
Yes. We regularly work alongside in-house engineers, share reviews and standards, and hand over cleanly when the engagement ends.
Where are you based, and do you work remotely?
We are based in Bengaluru, India, and work with clients across India and abroad. Most engagements run remotely, with on-site sessions where they help.
Ready to describe the problem?
A few lines about the problem, the systems involved and what a good outcome looks like is enough to start.