How We Work
What working together actually looks like.
Every stage answers one question, produces something you can review, and ends with a decision. Pick a stage.
Stage 01 · Discover
What is actually worth building?
What we do
- Talk to the people who will use, buy and support the product
- Review what exists today: systems, data, analytics and earlier attempts
- Separate the real constraints from the assumptions
What we need from you
- Access to the people who know the problem
- Existing documents, data samples and system access
What you get
- Discovery summary
- Goals and success measures
- Risks and open questions
Before we move on: We agree on the problem before anyone proposes a solution.
Stage 01 · Discover
What is actually worth building?
What we do
- Talk to the people who will use, buy and support the product
- Review what exists today: systems, data, analytics and earlier attempts
- Separate the real constraints from the assumptions
What we need from you
- Access to the people who know the problem
- Existing documents, data samples and system access
What you get
- Discovery summary
- Goals and success measures
- Risks and open questions
Before we move on: We agree on the problem before anyone proposes a solution.
Staying informed
You should never have to ask how it is going.
A predictable rhythm of updates and demos, so progress is visible without meetings for the sake of meetings.
- 01
A written update, on a fixed day
What was done, what is next, what is blocked, and any decision we need from you.
- 02
Demos, not slide decks
You see working software throughout the build, in a preview you can click through yourself.
- 03
One place for everything
Scope, decisions, questions and progress live in one shared place, not scattered across email threads.
- 04
A named point of contact
One person who knows your project end to end and answers for it.
Ground rules
What holds on every engagement.
Whatever the size or type of project, these do not change.
Scope changes are written down first
If something new comes up, we agree what it means for time and budget before building it.
Bad news travels fast
If something is at risk, you hear it from us early, with options, not at the deadline.
Nothing ships without review
Every change is reviewed and tested, and every release goes through a preview environment first.
Decisions are documented
Architecture and product decisions are written down with their reasons, so the next person understands why.
Ways to start
You do not have to commit to everything at once.
Most engagements begin in one of these ways. Tell us where you are, and we will suggest the right starting point.
Start with discovery
A short, fixed-scope engagement covering Discover and Define. You leave with a scope, a plan and an architecture you can take forward with us or anyone else.
Good forIdeas that need shaping, or a budget that needs a clear case.
Design and build
The full process, from the first conversation to launch and beyond.
Good forA defined website, application, AI or data product.
Take over an existing product
We start with an audit of the code, infrastructure and documentation, and stabilize before adding features.
Good forProducts whose original team has moved on.
Extend your team
Engineers working inside your process, with our review and delivery standards.
Good forTeams that need capacity or specific skills.
After launch
Launch is where the product starts earning.
Three levels of ongoing care. Which one fits depends on how much the product is expected to change.
Keep it healthy
Care
Security updates, monitoring, maintenance, bug fixes and routine technical care.
- Security and dependency updates
- Uptime and error monitoring
- Bug fixes and routine technical care
- Backup verification
Keep improving
Growth
Care plus content updates, performance improvements and agreed feature enhancements.
- Everything in Care
- Content and copy updates
- Performance improvements
- Agreed feature enhancements
Keep building
Dedicated Partner
Ongoing engineering capacity, priority support, roadmap execution and continuous development.
- Everything in Growth
- Ongoing engineering capacity
- Priority support
- Roadmap planning and execution
Continuous care is scoped to the product and the level of support your team needs. Talk to us about the right plan.
Project pricing is tailored to scope, functionality, design complexity and business requirements. Contact us to discuss your project.
Questions
Before you ask.
The questions we hear most often at the start of an engagement.
- Properly, only after Discover and Define. Before that, any fixed number is a guess. We can give a range early on, then a written proposal once the scope is agreed.
- They usually do. Changes are written down, estimated and agreed before they are built, so the plan and the budget stay honest.
- Yes. We can own the whole delivery, work alongside your developers, or take over from them. We agree at the start who reviews and approves what.
- A person who can make decisions, timely feedback, and access to the systems, data and content the project depends on.
- Chandigarh, India. We work with clients in India and internationally, and schedule calls around your working day.
Ready for stage one?
Every engagement starts with Discover: a conversation about what you are trying to change. Start there, and we will map out what the next stages would look like for you.
Intelligence → Innovation → Automation → Growth