We split the work cleanly. You stay at the keyboard, prototyping fast. Our senior engineers own the architecture, the code review, and the production craft. Our agents absorb the routine. Together, you ship features quickly without eroding the foundation.
The bootcamp is ~8 hours across 4 sessions(roughly 2 hrs each, fully recorded if you miss a block). It's front-loaded deliberately: by the end of the week your repo is configured, the Expandable Core Registry is written together, Claude Code is running with our skill files, and your first feature is pair-shipped.
After Week 1, your time commitment drops to one 60–90 minute sync per week, plus your own coding. The bootcamp is short on purpose — just enough to align your team and ours before the sprint rhythm starts.
A deeper written audit of your full codebase, scoped to ~1 engineer-day and delivered as PDF before bootcamp starts. Separate from the pre-contract "Top Risks" free audit.
Repo configured, Expandable Core Registry written together, Claude Code running with our skill files, first feature pair-shipped.
First structured sprints, first ADRs, PR review SLAs in effect.
3–5 items, sized and tagged (arch-review or standard). You propose, we guide.
Sprint review, architectural decisions, blockers, mentorship. Attended by your named Lead Engineer.
Code Review Agent runs first as a pre-check. A senior engineer reviews every PR before merge, within 24 business hours. PRs tagged arch-review get an architect's eyes in addition. No volume cap — we review as much as you ship.
Shipped / blocked / next. Async.
You push to your branch.
Style, obvious bugs, convention violations. Auto-detects core-surface and tags arch-review.
Within 24 business hours. Architecture, security, integration concerns. Architect joins on arch-review tags.
Either merged, or feedback ships and you iterate. ADR drafted automatically when relevant.
If we miss the 24-business-hour SLA on any PR, you get a credit of 0.25 days against the next invoice. No questions.
Runs first on every PR. Style, obvious bugs, convention violations, core-surface detection. Surfaces findings in PR comments for the senior reviewer who follows.
Keeps tickets, milestones, and priorities in sync with what's actually shipping. Surfaces blockers and progress updates so nothing falls through the cracks.
Bug triage, debugging, and hotfixes are included in the retainer. Every non-trivial fix ships with a regression test. After every P0, a short post-mortem lands as an ADR.
Post in shared channel with @selego bug — Debug Agent opens triage.
Label any issue with bug — auto-picked up, triaged, severity-tagged.
Anything Monitoring Agent flags is treated as a bug report automatically.
Your Debug Agent is on 24/7. Your senior engineer is on business hours — with P0 paging for production crises.
Each engagement has a named Lead Engineer — bio and LinkedIn shared before signing. They attend every weekly sync and own your architecture. Backed by a second Selego engineer for PR review coverage during time off. Any team change requires your approval.
Owns your architecture, runs your weekly sync, attends every escalation. Their LinkedIn lands in your inbox before you sign.
A second senior engineer who picks up review when your Lead is off. Same SLAs. Already familiar with your repo.
3-month minimum, then month-to-month. 30-day notice to end.
At exit we hand off the Expandable Core Registry, agent configurations, and all ADRs — they stay in your repo. Access credentials revoked within 24 hours.
1 month/year pause allowed. Agents keep running read-only; human review and syncs suspended; the 3-month minimum clock pauses with them.
If more than 50% of a month's work becomes us building end-to-end rather than reviewing yours, either side can flag it. We rebalance together. Neither side reclassifies unilaterally.
You own all code, ADRs, configuration, and skill-file customizations installed in your repo. Perpetual licence survives the engagement.
Our whitepaper and Convention Library are licenced perpetual, non-exclusive. Selego retains the right to keep using and improving them across clients.
Mutual NDA before kickoff. Credentials scoped to named team members, auditable, revoked within 24 hours of termination.
Capped at the previous 3 months of fees paid, per standard engineering-services practice.
Send us repo access. We'll come back within 5 business days with at least 5 concrete risks — yours to keep, no commitment.