What you get
- A written specification defining the milestone, acceptance criteria, and out-of-scope.
- A working code deliverable — could be a PR refactor, a new feature, a proof of concept, or a documented architectural fix.
- Engineering documentation — what we did, why, what’s next.
- A pod report — engineer profiles, working hours, communication preferences.
- A scoped proposal for continued engagement if you want to keep going.
Day-by-day timeline
Day 0–2: Discovery & access
20-min call with our CEO. NDA signed. Read-only repo access. We meet your tech lead and one stakeholder.
Day 3–5: Specification
We deliver the written spec. You review and approve. If you reject, the engagement ends here with no charge. If you approve, we start building.
Day 6–12: Build
Senior engineers + AI agents work in your stack. Daily Slack/Teams updates. PRs ready for your review by Day 10. Iteration through Day 12.
Day 13–14: Delivery & retrospective
Final PR merged or delivered. Documentation handed off. 30-min retrospective. You decide: continue, end clean, or refer.
Who it’s for
- CTOs with a specific bottleneck. Legacy module no one wants to touch. Backlog growing faster than capacity. AI feature stuck in proof-of-concept.
- CPOs with a delayed roadmap. Feature launching late. Need senior capacity now, not in 3 months of hiring.
- Founders preparing for a raise. Need a working MVP module to demo to investors. Risk-free path to ship in 2 weeks.
- Engineering leaders evaluating partners. Want to validate Pernix before committing to a 6-12 month contract. This is the cheapest way to know.
What we need from you
The sprint stays light on your team’s time. To make it work we need:
- Read-only repo access for the relevant codebase (or a representative module).
- A product owner for spec sign-off on Day 5.
- A technical contact available for clarifications during build.
- About 30 minutes per day for stand-ups and async review of PRs — no more.
- A signed mutual NDA before any access is shared.
Engagement and guarantee
The first sprint is at-risk. If we don’t deliver per the agreed written specification by Day 14, you owe nothing. If we deliver, the sprint is billed at a fixed price agreed up front.
Guarantee scope: the guarantee applies to the agreed written specification, scope, acceptance criteria, and delivery timeline. Changes requested mid-sprint reset the scope and may extend or rebill the sprint.
Continued engagements after the sprint are scoped based on team composition, seniority, and delivery model. Pricing is shared in the discovery call.
How we use AI safely
- We never send client code to public AI tools without explicit written approval.
- We use approved tools and tenant-scoped access controls.
- Human engineers review every AI-generated output before it lands in your codebase.
- AI does not define architecture or specifications — humans do.
- Client IP remains client-owned at all times.
- Sensitive code access is handled through agreed security policies and NDAs.
FAQ
Book your sprint
Three new client slots available for Q2 2026. Carlos personally takes every Day 0 call. 20 minutes. No prep required.