How we actually work with clients
Three ways to work with us, depending on whether you have a defined project, an ongoing capacity need, or a production system that needs steady upkeep. NDA-first, and the code is yours - under every model.
Three engagement models
None of these is a staffing arrangement - every engagement is engineering-led, scoped and delivered by people who own the outcome, not just the hours.
Fixed Scope
A defined project with a defined outcome
You know what needs to be built or modernized. We scope it, price it, and deliver it in phases with fixed checkpoints - so you always know where the project stands against the plan.
Good for: A single modernization, a new build, or an integration project with a clear start and finish.
Dedicated Team
Engineers who work inside your team
Add engineers who work your sprints, your tools, and your standups, for as long as you need the extra capacity. You direct the work; we staff and manage the engineering.
Good for: Ongoing product development, or filling a skills gap your internal team doesn't have.
Learn MoreRetainer / Ongoing Evolution
Continuous support for a system already in production
For systems that are done shipping v1 but never done changing - a standing arrangement for maintenance, small enhancements, and the occasional fire, without re-scoping a new project every time.
Good for: A production system that needs steady upkeep and periodic new features, not a single big project.
How a project actually starts
Tell us what you're working with
A short conversation or one of our assessment tools - what the system does today, what's wrong with it, and what you're trying to achieve.
We assess before we scope
For modernization and rescue work especially, we look at the system as it actually runs before committing to a plan - not before.
You get a plan, not a pitch
A written scope, a recommended engagement model, and a realistic timeline - phased where the work benefits from it, not a single high-risk cutover.
Work starts under NDA
Every engagement starts under NDA. Your code and your data stay yours, during the engagement and after it ends.
Team structure & communication
Every engagement has a single point of contact accountable for the whole thing, not a rotating cast of people you have to re-explain context to. Depending on scope, that point of contact coordinates a solution architect, backend and frontend engineers, and a dedicated QA function - sized to the work, not padded to justify a bigger invoice.
Timelines
Fixed-scope work ships in phases with milestone checkpoints rather than one delivery date at the end. Dedicated-team and retainer arrangements run for as long as the capacity or upkeep need exists - most start with an initial term and continue on a rolling basis from there.
How we work across timezones
We work with clients in the United States, United Kingdom, Australia, Canada and Europe, from our engineering centre in Mohali, India. That's not a virtual address or a sales office - it's where our team and our delivery actually sit.
Overlapping hours
We agree a block of real-time overlap with every client upfront, based on their timezone, so live discussion isn't left to chance.
Communication cadence
Most day-to-day work - code reviews, status updates, decisions - happens async and in writing, backed by a scheduled cadence of calls that matches the engagement model.
Response expectations
Your point of contact is reachable through the agreed overlap window, and async outside it - nothing waits for a single weekly call.
Collaboration tools
We work inside your existing tools - Jira, Slack, or Teams - rather than asking you to adopt ours.
Client point of contact
Every engagement has a single person accountable for it end-to-end, not a rotating cast you have to re-explain context to.
Frequently asked questions
What's your minimum engagement?
There's no fixed minimum - it depends on scope. A focused fixed-scope project and a long-running dedicated-team arrangement look very different in size. Tell us what you need and we'll tell you honestly whether it's a fit.
Do we own the code?
Yes. The code is yours - during the engagement and after it ends.
How do you handle time zones?
We work with clients in the United States, United Kingdom, Australia, Canada and Europe, from our engineering centre in Mohali, India, with overlap hours agreed upfront so communication doesn't become the bottleneck. Tell us your timezone when you reach out and we'll factor it into how we staff the engagement.
How is communication structured during an engagement?
A single point of contact who's accountable for the engagement, regular check-ins at a cadence that matches the model (sprint reviews for dedicated-team work, milestone check-ins for fixed-scope projects), and direct access to the engineers doing the work - not a relay through account management.
Can we start with something small before committing further?
Yes - a paid assessment or a small fixed-scope first phase is a common way to start, especially for modernization and rescue work where an accurate estimate depends on actually looking at the system first.
Not sure which model fits?
Tell us what you're working on and we'll recommend an engagement model honestly, before you commit to anything.