Working together
How engagements work
Four commercial models, one delivery standard. We will recommend the model that fits the certainty of your scope — and we are happy to change it later if the work changes shape.
Compare
Which model fits your situation
| Model | Best when | Commercials | Who owns delivery | Typical length |
|---|---|---|---|---|
| Fixed-scope project | Requirements are stable and well documented | Fixed price, milestone-based | Ibtivia owns delivery against an agreed specification | 4–24 weeks |
| Dedicated team | Scope will evolve; you want continuity | Monthly rate per team | Shared — you own the backlog, we own the throughput | 6 months+ |
| Staff augmentation | You need specific skills inside your own team | Monthly rate per engineer | You manage day to day | 3 months+ |
| Managed service | Ongoing operations, support or sustaining work | Monthly service fee against SLAs | Ibtivia owns the service level | 12 months |
Not sure? We usually suggest starting with a short paid discovery — typically two to three weeks — which produces a scope, an architecture sketch and a firm estimate. You can take that to any supplier, including not us.
From first contact to kick-off
What actually happens
No lengthy procurement theatre. Here is the sequence, and the timings we aim for at each step.
Scoping call — within 2 working days
A 45-minute technical conversation with an engineer from the relevant practice. Free, and under NDA if you prefer.
Written proposal — within 5 working days
Approach, team shape, assumptions, risks, timeline and price. Assumptions are listed explicitly so you can challenge them.
Contract and onboarding — 1 to 2 weeks
MSA and SOW, security and access onboarding, tooling setup and introductions to the named delivery lead.
Kick-off and first increment — week 3 to 4
The team starts. We aim to show demonstrable output within the first two-week cycle.
Governance
How we keep you informed
- Weekly written status covering progress, risks, decisions needed and anything that has slipped.
- Fortnightly demo of working software — not slides about software.
- Monthly steering with the engagement lead, covering commercials, scope changes and forward plan.
- One escalation path, named in the contract, with a response commitment attached to it.
- Quarterly retrospective on the relationship itself, not just the work.
IP & ownership
All work product, code and documentation is yours from creation. We take no licence-back and retain no rights.
Confidentiality
Mutual NDA before any technical detail is shared. Least-privilege access, and we use your systems wherever possible.
Continuity
Named team members, notice periods on changes, and documented knowledge transfer if anyone rotates off.
Exit
A defined exit plan in every contract: documentation, handover sessions and a transition window. No lock-in.
Questions
Commercial FAQs
Do you charge for the initial scoping call?
No. The first call and the written proposal that follows are free. We only charge once work begins, or for a formal paid discovery if you want a deeper scope up front.
Can we start small?
Yes, and we encourage it. A single engineer or a four-week proof of concept is a sensible way to test whether we work well together before committing to a programme.
What happens if the scope changes?
Change is normal. We handle it through a lightweight change note — impact on scope, time and cost, agreed before the work happens rather than discovered on the invoice.
Can we hire your engineers directly?
Yes. Every contract has agreed conversion terms. We would rather you hire someone good than lose the relationship over it.
Where are your engineers based?
Our head office is in Hyderabad, India. We build teams around the time-zone overlap you need, and the location mix is agreed in the proposal and does not change without your consent.
Tell us the problem, not the solution.
You do not need a specification to start a conversation. Describe the outcome and the constraints, and we will propose the shape of a team and an approach.