How we engage
From the first call to a system you can hand to your operators. No producers, no account managers, no surprises in the invoice.
Two-week paid discovery. We map the current system, the constraints, the failure modes, and the people who will own the result. You leave the discovery with a written technical plan you can show to anyone on your team.
If we are not the right fit after the review, we say so. The discovery fee is the only commitment.quadevs / posture
Inputs we expect
- Brief description of the problem and current pain
- Access to relevant systems read-only
- One stakeholder who can answer architectural questions in writing
What you receive
- System diagram of the proposed build
- Module list with risks and dependencies
- Hour estimate per module with a calendar window and a weekly burn cap
- Decision: proceed, refine, or end
Weekly demos, working software at each cycle. We ship to a staging environment that mirrors your production, not a sandbox. Every change has tests in the matching test project; nothing merges with a red CI.
We work async between demos. You get a written status note on Friday with what shipped, what is next, and what is blocked. No status meetings just to confirm the status note.
Working software, every week. Not a slide.weekly demo / contract
Telemetry, runbooks, and on-call coverage during the switch. We do not call something done until it has survived a week of real load. If a regression appears, we fix it, we do not file a ticket and disappear.
What you keep after cutover
- Deployment scripts you can re-run yourself
- Monitoring dashboards wired to your alerting
- Runbooks for the failure modes we have actually seen
- An incident contact tree with named humans, not aliases
Retainer or handover, your call. If we hand off, your team gets the runbook, the dashboards, and a recorded walkthrough of every system module. If you keep us on retainer, you get a fixed monthly envelope of hours for incidents, small features, and the boring upkeep that prevents the next incident.
We bill and budget by hours, with a weekly burn cap agreed up front. You see the running total, you can stop the burn at any week boundary, and we will not roll a surprise overrun into the next invoice.
- Time tracked per module against a written estimate
- Weekly summary of hours burned and what they bought
- Black-box delivery is not how we work. You see the codebase, the CI, the dashboards. Nothing happens behind a slide
- Scope expansion only via a written change request. We rather say no than quietly grow the bill