How we work
How an engagement runs, from assessment to handover
Engagements start small, are priced before they start, and are built so your team can run the result without us. Here is the whole shape; the call is for your specifics and the price.
Three phases
- 01
Assess
2–3 weeks, fixed price
Week 1: map workflows and data, and talk to the people who would use it. Week 2: test feasibility against your real data and security constraints. By week 3: a ranked roadmap with effort and risk per use case, and what to build first, or a written no.
More - 02
Pilot
typically 4–8 weeks
One use case to production. Every two weeks, a demo in your environment. Evaluations run in CI from the first merge. Monitoring and a runbook are in place before launch.
More - 03
Scale
ongoing, optional
Further two-week iterations, only while they earn their keep. Your engineers pair with ours until they run it alone. No retainer is required to start or to stop.
More
Formats and pricing
The assessment is fixed scope and fixed price, agreed up front. Pilot and scale work is quoted per milestone or on a time-and-materials basis with a weekly cap, whichever fits your budgeting. Scope is written down before work starts and reviewed at every two-week demo.
| Service | Format | Timeline | Team |
|---|---|---|---|
| AI Enablement | Fixed-price assessment, then a milestone-priced pilot that takes one use case to production. | 2–3 weeks assess, ~4–8 weeks pilot | 1 lead engineer + 1 senior engineer |
| Product Engineering | Scoped build with a demo every two weeks; milestone or time-and-materials pricing with a weekly cap. | Typically 6–16 weeks per product phase | 1 lead + 1–2 senior engineers |
| Platform & Data | Audit first, then an infrastructure-as-code build with handover sessions for your platform owners. | Typically 3–10 weeks | 1 cloud architect + 1 data/ML engineer |
The assessment is fixed scope and fixed price, agreed up front. No retainer is required to start or to stop.
What we need from you
- Access to the systems the work depends on.
- A named person who would use the result every week.
- Someone who can decide security questions.
Without these the work slows down, and we will tell you.
Not a fit
- You need a large staffing bench or a 24/7 managed service desk.
- You want a demo for a board meeting rather than a feature customers will use.
- You are not able to give engineers access to the systems the work depends on.
The longer list, with reasons: what we say no to.
What you own
Code, infrastructure, and docs live in your accounts from day one. Nothing transfers at the end because nothing ever left. The checklist we hand over against is public: the definition of done.
Start with the 30-minute call.
We reply within two business days with a yes, a no, or the one question we need answered first.
Book a free 30-minute scoping callWe reply within two business days. No deck or RFP needed.