Three add-ons for the work around the code.
A pipeline to ship through, a design to build from, and tests that keep it all working. Each add-on joins a lab’s sprint at a flat price, agreed with the scope before the sprint starts, and works on that scope.
DevOps: Shipping should be the boring part.
Pipelines, cloud infrastructure and monitoring, built in the same sprint as the code that depends on them, so a deploy stops being an event and problems surface before your users report them.
$250/sprint
Flat, whether the sprint runs one week or two. Added to any lab, for that sprint’s scope.
WHAT IT COVERS
CI/CD pipelines
Build, test and deploy on every merge, on GitHub Actions, Vercel or Railway.
Cloud architecture
AWS or GCP, load balancing included, sized for the traffic you have and the traffic you expect.
Docker and Kubernetes
Containers and clusters when the product needs them, and not before.
Monitoring and alerting
Sentry and Datadog wired in, with PagerDuty hooks for the alerts that matter.
Database performance
Read replicas and connection pooling once queries start to queue.
Security hardening
Access, secrets and configuration tightened before due diligence asks about them.
ADD IT WHEN
- ›Deploys are manual, or amount to pushing to main and hoping.
- ›You are scaling on infrastructure that was not built for it.
- ›Environment problems eat the time meant for testing.
- ›Technical due diligence is coming and the infrastructure has to look mature.
SKIP IT WHEN
- –You already have a strong DevOps engineer in-house.
- –You need 24/7 on-call cover. This add-on builds the systems; it does not staff a rota.
UI/UX: Designed and built by the same sprint.
User flows, design systems and interfaces, drawn alongside the engineers who build them, so what ships is what was designed and nothing is lost in a handoff.
$250/sprint
Flat, whether the sprint runs one week or two. Added to any lab, for that sprint’s scope.
WHAT IT COVERS
User flows
Research and flow mapping before anything is drawn, delivered as a FigJam board.
Design systems
Tokens, type and components in a Figma library your team can extend.
Clickable prototypes
High-fidelity, so decisions get made on something that behaves like the product.
Responsive screens
Landing pages, dashboards and admin tools, at mobile, tablet and desktop sizes.
Component libraries
The design tokens carried through to React components, in Figma and in code.
Accessibility audits
Checked against WCAG, with the fixes made rather than listed.
ADD IT WHEN
- ›The product still looks like the MVP, and it is costing you enterprise deals.
- ›You want a design system that scales, not a folder of static screens.
- ›Designs keep getting lost on the way to code.
- ›You want one team to design and build, with nothing to translate in between.
SKIP IT WHEN
- –You need brand identity. Logo and positioning come before this work.
- –You want designs to hand to your own developers. This add-on works inside a lab sprint.
QA & Testing: Catch it in CI, not in a support ticket.
Every lab sprint already gets release checks from its fractional QA. This add-on builds a suite you keep: automated tests and quality gates that run in your CI on every change, long after the sprint ends.
$250/sprint
Flat, whether the sprint runs one week or two. Added to any lab, for that sprint’s scope.
WHAT IT COVERS
Automated test suites
Unit, integration and end-to-end tests in Jest, Playwright or Cypress.
Critical-path tests
Sign-up, checkout and the other flows that earn money, on the devices your users carry.
Regression runs
The whole suite on every change, so a fix cannot quietly break something else.
Quality gates in CI
A pull request with failing tests does not merge.
Load and performance testing
Where capacity runs out, found before real traffic finds it.
Reproducible bug reports
Steps, environment and a screen recording for every issue raised.
ADD IT WHEN
- ›You ship fast and things break in production.
- ›You have developers but nobody dedicated to QA.
- ›A funding round is coming and you need to show technical maturity.
- ›Enterprise buyers are asking how you test.
SKIP IT WHEN
- –You are pre-MVP. Test coverage at that stage is premature.
- –You want manual testing only. This add-on is automation first.
› QUESTIONS
Asked about add-ons
It joins the next one. A sprint’s scope is fixed once it starts, which is what keeps its price fixed, so an add-on is agreed along with the next sprint’s scope.
No. Add-ons are flat per sprint, whatever its length. A two-week sprint with QA & Testing costs the lab’s two-week price plus $250.
The fractional QA on every lab checks each release before it reaches your users. QA & Testing builds a suite you keep: automated tests and quality gates that run in your CI on every change, after the sprint is over.
No. An add-on works on the sprint’s agreed scope. Work outside it is scoped and priced on its own. If you want that specialist on something else — an audit of its own, a design project beside the build — we scope and price it separately, on its own contract.
No. The DevOps add-on builds the pipelines, monitoring and alerting your team runs with. It does not staff an on-call rota.
You do, from day one, in writing. Figma files, infrastructure code and test suites sit under your own accounts, like everything else a sprint ships.
Name the add-on on the scoping call.
We agree it with the sprint’s scope and price before anything starts, and nothing is billed until then. The first 14 days are on us.
◈ 14-DAY GUARANTEEIP YOURS FROM DAY 1NO LONG CONTRACTS