07 · Journal · How we workVol. 10 · Q2 2026kleiotechnology.com

How an engagement with us actually works.

Discovery sprint, pod, managed platform, or staff augmentation. The model depends on what you need; the discipline does not change.

Habakkuk 2:2

Write the vision, and make it plain upon tables, that he may run that readeth it.

Back to journal Talk to us

§ I — Cover concept

The context behind the article.

Journal 040

5 min

Image direction

How we work

5 min

Article

Discovery sprint, pod, managed platform, or staff augmentation. The model depends on what you need; the discipline does not change.

Why it belongs in the journal

This entry exists to make the operating logic visible: not just the system we would build, but the constraint, tradeoff, or failure mode that forced the architecture to matter in the first place.

§ II — Article

How an engagement with us actually works.

Four ways to start, one way to operate

Every engagement we run uses one of four commercial shapes. The discipline behind the work is the same. What changes is scope, commitment, and ownership.

The four shapes

Discovery Sprint — Two weeks. Fixed price. A small team of ours sits with yours, reads the runbook, and ends the sprint with a written architecture letter and a roadmap. You keep the document whether you continue with us or not.

Pod (named team) — Four to eight engineers, embedded with your organization for six to eighteen months. Named, not rotating. Senior, not junior-on-junket.

Managed Platform — We run the platform we built. Twenty-four-seven on-call, defined SLOs, a monthly retainer, and quarterly business reviews.

Staff Augmentation — Senior engineers paired with your team. We do not send people who are still learning the craft on your dime.

The discipline that runs through all four

An architecture decision record opens every engagement. You keep it.
A standard MSA covers IP ownership, named-team continuity, and exit clauses written in plain English.
Insurance — $5M E&O, $5M cyber, $2M general — certificates on request.
Quarterly business reviews with your CFO and CTO covering SLO performance, spend versus plan, and risk register.

What week one looks like

We sit with your team. We read the runbook. We do not present anything. The architecture letter shows up in week two.

What week two looks like

We ship to production. Always.

What handover looks like

Docs, dashboards, runbooks, and a team that does not need us. Then we leave. Coming back later is a normal outcome; needing us forever is not.

The proof of work is what the team can do six months after we are gone, not what looked impressive on the way in.

§ III — Reading note

What the article is really about.

Operating tension

Discovery sprint, pod, managed platform, or staff augmentation. The model depends on what you need; the discipline does not change. In practice, the hard part is usually not implementation syntax but aligning delivery, controls, and operator trust so the thing can survive contact with a real team.

Kleio view

We treat these articles as public design memos: short, opinionated, and anchored in systems that have to be bought, operated, and defended long after launch week.

§ III — Continue reading

Three adjacent articles.

Cloud Computing

Modernization is a pipeline, not a rewrite.

We killed a $400K rewrite in week two and replaced it with a three-tier modernization pipeline. Eleven modules extracted, 19,000 lines of dead code retired, drift down 62% — without a single big-bang cutover.

Audit before you automate.

An association almost spent $180K automating a workflow that ate twenty-four hours per year, while an 8,680-hour problem sat untouched. The fifteen-minute audit that caught it is the cheapest piece of work in any AI engagement.

Agentic AI

MCP servers are the orchestration layer, not the demo.

Most AI tooling lives one paste away from the systems it could help with. Model Context Protocol servers close that gap without giving up the security posture an enterprise can defend.

Back to journal