At a glance

The four phases
of every engagement.

From first call to long-term retainer — here's the shape of working with Cynep.

01 — DISCOVER

Listen first

Short paid discovery — we leave with a written scope, architecture sketch and fixed estimate.

02 — BUILD

Ship in slices

Weekly demos, working software in production within four weeks. No big-bang launches.

03 — HANDOVER

Docs & runbooks

Architecture decision records, runbooks, and pair-on-call rotations until your team owns it.

04 — CARE

Stay close

Optional retainer for ongoing improvements, on-call backup and a quarterly architecture review.

In detail

What each phase
actually delivers.

We share artifacts at the end of every phase — written, reviewable, and yours to keep.

01 Discover · 1–2 weeks

Listen first.

We spend a focused week or two with your team — interviews, architecture review, code spelunking. You get a written scope, an annotated architecture diagram, and a fixed estimate. If we're not the right team, we say so.

  • Stakeholder interviews
  • Architecture review
  • Written scope document
  • Fixed-price estimate
02 Build · 4–12 weeks

Ship in slices.

Working software in production within four weeks. Weekly demos, two-week milestones, and a real burn-up chart you can check without asking. No big-bang launches; nothing leaves staging without observability and rollback.

  • Weekly demos & check-ins
  • Production-grade code from day one
  • CI/CD & observability included
  • Public progress dashboard
03 Handover · 2 weeks

Docs and runbooks.

We don't leave when the last ticket closes — we leave when your team can run it without us. Architecture decision records, runbooks for the top failure modes, and a pair-on-call rotation during the first two weeks of full ownership.

  • Architecture Decision Records
  • Operational runbooks
  • Pair on-call rotation
  • Knowledge-transfer workshops
04 Care · Ongoing

Stay close.

Optional retainer. We're available for on-call backup, tricky incidents, and a quarterly architecture review. Most clients keep us on a small monthly retainer — not because they need to, but because they want to.

  • Quarterly architecture review
  • On-call backup & incident support
  • Continuous improvement backlog
  • Direct Slack channel access
Operating principles

How we make decisions
when no one is watching.

The rules we hold each other to — and that you can hold us to.

Working software, weekly

If you can't see it running by Friday, the plan is wrong. We slice for delivery, not for tickets.

Document what we choose

Every non-obvious decision lands in an ADR. Future engineers — yours and ours — will thank us.

Bias to simpler

Three boring services beat one clever one. We ship what your on-call can debug at 3am, not what reads well in a talk.

Ready to start with discovery?

Most engagements begin with a 1–2 week paid discovery sprint. Fixed scope, fixed price, written scope at the end.