Skip to content
Vol. 06 · Issue 14 Filed under: Trust Documents Last revised Q1 2025

DaWabbit Labs · The 14-Day Guarantee

Ship a deployable artifact in 14 days,
or the sprint is on us.

This is not a marketing slogan. It is a contract clause. Below you will find the plain-English terms of our first-sprint-or-free promise, the receipts behind it, and the four things we commit to before you send us a single line of code.

312 sprints delivered without a refund claim ◆ 58h median ramp from contract → first commit ◆ 14.2d median time to first production deploy ◆ 92% client retention · last 8 quarters ◆ NPS 71 · Q1 2025 survey, n=204 ◆ 312 sprints delivered without a refund claim ◆ 58h median ramp from contract → first commit ◆ 14.2d median time to first production deploy ◆ 92% client retention · last 8 quarters ◆ NPS 71 · Q1 2025 survey, n=204 ◆
Document DW-GUAR-14 · rev. 2025-03
Counter-signed by M. Halverson, Head of Delivery
Effective Every sprint since launch, 2019

Section 01 · The Terms, in Plain English

What we promise, what starts the clock, and what happens on a refund.

  1. Clause 01

    The promise.

    Within fourteen (14) calendar days of your first sprint kickoff, DaWabbit will deliver a deployable artifact against an agreed acceptance criterion. The artifact is whatever you need it to be — a shipped feature branch behind a flag, a staging deploy wired to your staging environment, a working API endpoint, a clickable prototype, or a signed-off design system component. We will commit to the artifact in writing in the kickoff Slack channel before the clock starts.

  2. Clause 02

    What starts the 14-day clock.

    The clock starts on the later of (a) the moment our contract countersignature lands in your inbox, or (b) the start of the first business day after you provision repo access. We pause the clock, in writing, if you request a scope change that materially alters the acceptance criterion. We will not pause it for ordinary review cycles.

  3. Clause 03

    What counts as the artifact.

    A deployable artifact is (i) merged code on a branch you can deploy, (ii) with documented acceptance criteria from the kickoff doc, (iii) reviewed and signed off in writing by your named DaWabbit lead and a stakeholder you name. A slide deck, a Loom, a Figma frame, or a Jira ticket without merged code is not, on its own, an artifact under this clause.

  4. Clause 04

    What happens if we miss.

    If we miss the artifact by day 15, the entire sprint is free. We refund the sprint invoice in full within five (5) business days of the missed deadline, in the same currency you paid in. You keep the code, you keep the repo history, you keep the Slack thread. You do not have to write us a postmortem, sit through a debrief, or commit to a second sprint. We have delivered 312 consecutive sprints without paying out a refund.

  5. Clause 05

    What we do not promise.

    We do not promise user growth, fundraising outcomes, or revenue targets. We do not promise that the artifact will be the one your customers eventually see in production — we promise it will be the agreed thing, delivered on time, against the acceptance criterion both sides signed. We position as on-demand augmentation, not as a replacement for your permanent team.

Signed, DaWabbit Labs, Inc. · 2261 Market Street #4818, San Francisco, CA 94114

Section 02 · The Receipts

Proof, not puffery. The numbers behind the guarantee.

312

Sprints delivered without a refund claim

Consecutive. Every sprint since launch in 2019 has hit its 14-day artifact commitment on the agreed acceptance criterion.

58h

Median ramp: contract signed → first commit

Verified via time-tracked GitHub audit logs across all 2024 engagements. The clock starts when the ink dries; we are in your repo before the weekend.

14.2d

Median time to first production deploy

Versus an industry median of 47 days. G2 named us to the 2024 Fastest Implementation list for IT Services on the strength of this number.

92%

Client retention · last 8 quarters

Of 612 lifetime clients, the majority of the active book renews sprint after sprint. Most came back for the second sprint because the first one shipped.

Section 03 · Delivery Obligations, Sprint 01

Five things we commit to in writing before the sprint starts.

Tick-box language, taken straight from the master services agreement. If we miss any of these, treat it as a Clause 04 miss and call the refund.

  1. 01

    Repo access & environment parity.

    Within 24 hours of contract countersignature, we receive admin access to your repo, a staging environment we can deploy against, and read access to your issue tracker. We mirror your folder structure, branch conventions, and CI on our own scratch repo before the kickoff call.

  2. 02

    A named lead with shipped-at-scale credibility.

    Every sprint has one named human lead — drawn from our 38 in-house engineers — who is in your dedicated Slack channel, owns the kickoff doc, and signs the 14-day artifact handoff. Every lead has shipped at scale at a company that went through YC, a16z, or Sequoia.

  3. 03

    Async standups & a nine-minute reply SLA.

    Daily written standups land in your channel by 10:00 PT. The named lead commits to a nine-minute average reply time during business hours — measured, not aspirational. No meeting required for the first three days. We earn the calendar slot.

  4. 04

    Weekly billing, one-sprint minimum, no lock-in.

    Invoiced every Monday for the prior sprint-week, net-7. The minimum engagement is a single sprint. 480+ startups have used shorter sprints to bridge fundraising gaps without taking on a full-time hire.

  5. 05

    You own everything we build. Always.

    Work-for-hire IP assignment on the contract. The repo, the code, the documentation, the design files, the notes — all transfer to your ownership the moment the invoice is paid. We retain no license, no attribution requirement, and no resale rights. If we part ways after sprint one, the only thing you owe us is the bill for sprints you kept.

Spec rev. DW-SPEC-DLV-05 · countersigned in the master services agreement · reviewed quarterly

Section 04 · The Rebuttals, Answered

Five questions founders ask us before they book the call.

"What if my acceptance criterion is fuzzy?"

That is the most common situation and it is exactly why the kickoff doc exists. Before the clock starts, our lead sits with you (or async, in writing) and writes down the artifact in plain language, with a measurable acceptance criterion both sides can tick. If we cannot agree on a criterion in the first 48 hours, we tell you up front and you keep your money.

"What if our scope changes mid-sprint?"

We pause the 14-day clock in writing for any scope change that materially alters the acceptance criterion. Ordinary review feedback, copy tweaks, and design polish do not reset the clock — that is our problem to absorb. A pivot from "ship the search endpoint" to "ship an entirely new auth model" does, and we will write the amendment before we start the new work.

"Who owns the IP? What happens if we part ways after sprint one?"

You do. Work-for-hire, assigned on the master agreement. We retain no license, no attribution, and no resale right. The repo, the design files, the docs, the Slack transcript — all of it transfers to you on the day the invoice clears. If you stop after sprint one, the only thing you owe us is the single sprint's invoice. No exit fee, no kill clause, no non-compete.

"Have you actually paid out a refund, or is the guarantee theoretical?"

We have not, across 1,840+ sprints for 612 clients since 2019. We had two near-misses in 2021 — both cleared at hour 320 of day 14 after a documented scope expansion reset the clock. The guarantee is, on our books, an insurance policy we have never had to cash.

"What happens after the first 14 days?"

You choose. Most clients renew — we hold a 92% retention rate across the last eight quarters. Some convert the sprint lead into a part-time fractional CTO model. Some stop, take the artifact, and hire in-house. All three outcomes are priced into our business and we will not pressure you into any of them. If you decide to leave, you leave with the code, the docs, and the Slack history.

Section 05 · Next Step

The guarantee holds.
The next move is yours.

A 30-minute Sprint Call with a DaWabbit engineering lead. We will read your backlog before the call, name the artifact in writing on the call, and have an engineer in your repo within 58 hours of countersignature.

Book a Sprint Call Read the Sprint Shape

Or call us directly — +1 (415) 555-0173 · [email protected]

First sprint is free if the artifact misses. 312 for 312. The next one is yours.