Stride
How it works

The full breakdown.

The engagement runs as three stages that match the offer. Stages 1 and 2 are the step. Stage 3 is the stride. Stride itself, the software, stays complimentary for as long as you use it.

stage 01

Install and setup

2 days, on-site or remote

Two days that install the tools, teach the primitives, and ship the first app end to end.

  • before day 1Security hygiene (disk encryption, password manager, MFA on GitHub and Anthropic), corporate VPN, GitHub org access, Anthropic Claude Max or Team seat, Linear workspace.
  • day 1, installHomebrew, Node, Python, git, Claude Code CLI, app-starter cloned, Stride installed and MCP-connected. Git, atomic commits, kanban primer.
  • day 2, shipPick one Linear card from discovery scope. /linear:plan-work drafts it. /linear:start cuts the branch. /commit lands atomic commits. /linear:finish opens the PR. Dashboard live in your environment.
deliverableOne real internal app running end to end by the close of day 2, in an environment InfoSec will approve.
stage 1 / installday 2
Claude Code installedprimitives
Stride MCP-connected to Linearstride
app-starter clonedrepo
atomic commits, kanban primerhabits
first app shipped end-to-enddeliverable
stage 02

Weekly support

1 day a week, for three weeks

The workflow only becomes real when you're building alone. I book one day each week to catch anti-patterns while the habits are still forming.

  • week 1Review your first independent piece of work. Spot missed atomic commits, kanban drift, premature optimisation. Fix early.
  • week 2Second app ships. Patterns repeat, confidence grows.
  • week 3Third app. You're increasingly self-sufficient. You can hand the URL to your line manager.
deliverableThree apps shipped by end of week 3. You running the workflow alone, without supervision.
stage 2 / weekly reviewweek 1 of 3
reviewing ENG-144 (vendor cost tracker)
- one big commit, mixed concerns
+ split into 3 atomic commits
+ /linear:plan-work used correctly
no premature optimisation
kanban discipline holding
stage 03

Ad-hoc support

Monthly check-ins, then by demand

Past three weeks, support drops to what you actually need. Stride itself stays complimentary.

  • monthlyA short check-in for the next couple of months, then ad-hoc.
  • topics by demandHosting (VPS vs cloud vs PaaS), database vs flat file, when to stop refactoring, telegraphing work through Linear, spotting premature optimisation before it eats three days.
  • continuityAndy Mindel is Webventurer's co-founder and available as backup on every engagement. Two people, not one.
deliverableYou shipping apps on your own, with a known path back when something needs judgement.
stage 3 / ad-hocyour stride
apps shipped8 and counting
vendor fees£2k each£0
codeyour GitHub org
boardyour Linear
supportmonthly check-in
04 / the stack

The stack underneath.

A working app on day one. A week of toolchain decisions already made. Boring, opinionated, proven.

01engine

Claude Code

Anthropic's terminal-based coding agent. Reads and writes across your repo, runs your tests, uses MCP tools, executes shell commands under your permission. The thing that actually writes code.

your code, your promptsnever trained on
02shipping system

Stride

A thin wrapper around Claude Code that implements kanban on Linear. Plain-English brief in, well-scoped Linear card out. Branches cut, atomic commits landed, PRs opened. The bit you don't have to think about.

commands/linear:plan-work, /linear:start, /commit, /linear:finish
03issue tracker

Linear

Fast, modern issue tracker. Jira's sleeker cousin. Your work is visible without you having to write a status report. One URL to your line manager and they see everything.

lanesbackburner → backlog → todo → doing → review → done
04repos

Starter repos

A working web app or Python scaffold from the first commit. So you don't spend three days picking a stack. React + Vite + ShadCN + Biome + tests for web. Tooling pre-wired for Python.

githubwebventurer/app-starter, webventurer/python-template
05 / why kanban

Why kanban, specifically, and not sprints.

One human orchestrating AI agents is not a classic team. Agents have no commitment cost and they work in parallel, so sprint boundaries become artificial lag. The real WIP caps sit at review bandwidth and merge coherence. Both are bottlenecked on you, the human.

Kanban handles that natively. Cards pull through lanes when there is capacity. No sprints, no ceremonies, no planning meeting, no retro that nobody wants.

01backburner
02backlog
03todo
04doing
05in review
06done
06 / procurement

What your line manager will ask.

Q

Does Anthropic train on our code?

No. On a Claude Team seat, prompt-training prohibition is contractual. On a personal Max subscription, it's a toggle you own. Either way, the answer is no.

Q

Where does the code live?

Your GitHub org. Your accounts. Your infrastructure. Webventurer does not host anything. If you leave Webventurer, nothing is locked in. Everything keeps working in place.

Q

What about GDPR and leavers?

The full procurement brief covers DPA, the private GitHub org, the Claude Max subscription or 5+ Team seats requirement, and Anthropic's Commercial Terms. Shareable with InfoSec and your DPO.

Q

What does year one cost?

Around £6k ex VAT. £5k is my engagement. The rest is Anthropic and Linear subscriptions and hosting. Three replaced vendor reports pay it back. Every report after is upside.

Next step

Map your data to Linear cards.

30 minutes, free. We walk through your actual data sources and map them to Linear cards before any money is spent. You leave with a one-page scope.

Book a 30-min discovery call

Usually booked within the week.