A small set of engagement shapes, named explicitly. Milestone-billed where work is bounded; retainer-plus-milestones where the relationship is the work. No multi-year master services agreement before you've seen us ship.
The shape of an IVBIS engagement is fixed. The size of each stage isn't. Discovery is two weeks or four. Delivery is two waves or six. The structure stays. The cadence is yours.
Read the system as it actually runs. Name the outcome. Find the load-bearing constraints.
Build the architecture map and a plan that traces to the PRD. PlanTrace produces the lineage.
Iterate in waves. AI agents draft and test. Senior engineers gate every change. ArchTrace enforces.
Runbooks, dashboards, on-call rotation. Same engineers do the handover who did the build.
We don't try to be all things. Engagements fit one of three shapes, sized and priced honestly. Pick the smallest one that solves your problem; bigger ones exist when the answer is genuinely a longer relationship.
A short, fixed-fee engagement to frame the problem honestly before anyone signs a delivery commitment.
A bounded delivery engagement — a module, a migration, a greenfield service. Milestone-billed against a plan signed up front.
A standing engagement across multiple waves and a programme of work. Retainer plus milestone, named team, multi-quarter horizon.
We don't publish a rate card because a rate card invents a precision the work doesn't have. Pricing is by milestone for delivery, fixed-fee for discovery, and retainer-plus-milestone for strategic partnerships. The number is the price for the outcome we both signed off on, not a function of how many hours got logged.
What that buys: a single price that covers the whole stage, a single point of accountability if it slips, and no incentive on our side to keep the work going. We are slightly worse off when an engagement takes longer than planned, which is the structural property a buyer should actually want from a vendor.
What it doesn't buy: change-order revenue. If scope expands meaningfully, we re-plan rather than re-bill — and we say so before we start. A new wave is a new wave. An old wave doesn't get more expensive halfway through.
A short list of the questions vendor management always asks, with the answers in plain language. If you'd rather skip the back-and-forth, the same content is in a single-page PDF below.
Standard cover is in place from a top-tier carrier; higher limits can be added for the engagement at marginal cost.
We don't take production data into ours. AI agents run in the client cloud or on a bring-your-own-key model. Records on request.
We use the model providers and infrastructure you'd expect, and we publish the list. We don't add anyone to it without telling you.
Code we write for you is yours, fully assigned. Reusable agents and playbooks remain ours and are licensed to you for the engagement and beyond.
Either side can exit on 30 days. Handover is included, not a separate line item. The system you take with you runs without us.
Reports and the DPA template are available under NDA on request. We're happy to sign yours instead of using ours.
Start with a sentence about the engagement you have in mind.
We reply within two business days. We don't add you to a mailing list.