Process Basecamp-first 13 years iterated
Most engineering projects fail at coordination, not code. Our process exists because we have run hundreds of them and learned where the friction lives. Project management on Basecamp, written weekly status reports, two-reviewer rule on every production branch, full handover documentation. Boring on purpose.
Process
Two-week discovery for every multi-week project. Architecture review, stakeholder interviews, risk audit, written fixed-price quote. No surprises after kickoff.
Process
Every hour goes into a Basecamp todo with a written summary. Weekly Friday status report, optional 30-minute call, two-reviewer rule on every production branch. You always know what shipped and what is next.
Process
Two-reviewer rule on production branches, automated linting and testing gates, security review before any auth or payment touch. The same standards we use on our own products.
Process
Every project ends with operational documentation, runbooks, deployment guides, and a 30-day warranty window. Your team can take over without losing context.
Process
EST, PST, and IST coverage. Async-first by default through Basecamp. Daily written todos, weekly written status, optional video reviews. Timezone difference becomes a productivity feature, not friction.
How a typical engagement runs
The five pages above describe each phase of work. Below is what runs across all of them. Same shape on a 20-hour pay-as-you-go block as on a six-month fixed-price build.
Every engagement runs on Basecamp. Todos for every task, message-board updates, complete written history of every decision. No "trust us" emails, no Slack DMs that get lost.
See engagement model ›Every Friday: what shipped, what is in progress, what is blocked, hours consumed, hours remaining. Written, archived, auditable. Risks surface the day we know, not the day before launch.
See sprint cadence ›A 30-minute call every week if you want one, optional otherwise. Most clients drop it after week three because the written report is enough. Available when you need it.
Book a 30-minute slot ›Staging server you can log into, git repository you can audit, branch and pull-request history you can review, code-review comments visible to you. Engineering is not a black box.
See review standards ›0
missed kickoff dates in the last 24 months
Discovery commits to a kickoff date. We have not missed one. If we cannot, we do not commit.
Ready to start a discovery?
Discovery is the only commitment for the first two weeks. Build phase only kicks off after you sign off on the discovery output.
WBComDesigns is amazing. The WP plugins and themes are of top notch quality with lots of features and updated very frequently. Supports are very responsive and helpful. I use Reign with TutorLMS, and the experience is surprisingly smooth.…