← Home Process

How an engagement runs

Four phases, clear deliverables at each one, and no surprise scope. Here's what actually happens at each step.

01

Discover

A short technical review of your current setup — infrastructure, codebase, team workflows, and goals. We ask about constraints (budget, timeline, existing tooling) before proposing anything.

Typical duration
  • 2–5 business days
Deliverable
  • A written summary of findings and recommended direction
02

Plan

A scoped plan with clear deliverables, milestones, and a fixed timeline — never an open-ended retainer unless that's specifically what you want.

Typical duration
  • 3–7 business days
Deliverable
  • A project plan with cost, timeline, and defined scope you approve before work starts
03

Build

Implementation happens directly in your repositories and cloud accounts, with regular check-ins so you always know where things stand. Infrastructure as code, every change reviewed and version-controlled.

Typical duration
  • Varies by scope — most engagements run 2–8 weeks
Deliverable
  • Working, deployed infrastructure or software, plus documentation
04

Operate

Handover with full documentation once the build is done — or ongoing support if you want us to keep monitoring and iterating on what we built.

Typical duration
  • Ongoing, month-to-month, cancel anytime
Deliverable
  • Runbooks, architecture docs, and monthly reliability reporting if ongoing
FAQ

Common questions

Do you work on fixed price or hourly?
Most engagements are fixed-scope with a fixed price, agreed after the Discover phase. Ongoing support in the Operate phase is billed monthly.
How long does a typical engagement take?
Most infrastructure and CI/CD engagements run 2–8 weeks. Advisory and consulting engagements can be a single session or an ongoing monthly arrangement.
Do we own the code and infrastructure after you leave?
Yes. Everything lives in your repositories and cloud accounts from day one. You get the credentials, the documentation, and no lock-in.
Can you work alongside our existing team?
Yes — most engagements involve working directly alongside your engineers, not replacing them.
What if our project turns out to be too small to need you?
We'll tell you. Not every problem needs a consultant, and part of Discover is figuring out whether you actually need one.

Ready to start with Discover?

It's a short technical review, not a sales call. Send us what you're working on.

hello@infinitum-ops.com