Ship fast, hand off clean, no lock-in.
AI services · internal AX tools · Web3 dApps handed off as 4 deliverables — code plus AI-readable docs, E2E guardrails, and operational runbooks.
// auth.ts
async function signIn(token) {
- if (result === null) return
+ if (!result?.ok) throw err
return result.user
}3 areas. All ones we use ourselves every day.
AI Services
Production-grade AI products for internal or external users — not demos.
Internal AX Tools
Accelerate team workflows. AI Usage Tracker itself is one.
Web3 dApps · Tokenomics
From contracts to token sales. 40-50K DAU in production.
Not just working code.
Handed off as a 4-piece set — code · AI-readable docs · E2E guardrails · operational runbook.
Working Code
Ships to your GitHub
// auth.ts
async function signIn(token) {
- if (result === null) return
+ if (!result?.ok) throw err
return result.user
}Two-Layer Docs
AI docs · human docs split
E2E Suite
Playwright + CI integrated
Operational Runbook
Deploy · incident · monitoring
Two doc layers — so both humans and AI understand the system.
Human docs stay as-is. AI docs split into 4 startup + 4 in-progress — so agents like Claude Code absorb system context and decision history immediately.
Standard artifacts
Docs developers and managers read directly
- README.mdProject overview · setup
- ADR (decisions)Key architectural decisions
- API docsEndpoints · schemas
- Ops guideDeploy · incident · monitoring
Startup context
4 files an agent reads on first encounter with the project
- CLAUDE.mdAI agent operating rules
- CONTEXT.mdProject context · tech stack
- SPEC.mdFeature specs · invariants
- DESIGN.mdDesign system · UI decisions
In-progress logs
4 files that accumulate living history every session
- state.mdCurrent focus · next actions
- worklog.mdPer-session work log
- decision.mdAlternatives compared, then decided
- backlog.mdBacklog · priorities
See sample — actual state.md / decision.md excerpts (anonymized)
### Current focus
ACME payment pipeline — Stripe webhook
retry queue + idempotency validation
### Next up
1. failed_webhook table + retry policy
2. /api/billing/webhook idempotency-key check
3. E2E: 3 scenarios via stripe-mock
### Blockers
None
### Needs human call
- Refund policy — prorated vs full
- Membership downgrade timing## 2026-XX-XX: Payment retry — queue vs cron
- **Choice**: failed_webhook table + cron retry
- **Alternatives considered**:
- (A) Bull/SQS queue — fast but adds infra
- (B) Table + cron (picked) — simple, easy to monitor
- **Reasoning**: traffic is small (<10/s).
Ops overhead lower than introducing a queue
- **Impact**: schema · webhook route · cron
- **Rollback**: can migrate to a queue later3-tier test scenarios — from PR guards to full coverage.
We don't run every test the same way. Split into 3 tiers by when and what to verify — fast PR guards, daily core flows, periodic full coverage.
CI/CD smoke
Login · checkout · homepage — only cases you must catch on break. Auto-runs on every PR; failure blocks merge.
Daily key flows
Flows users actually use often. Runs nightly → results ping Slack. Broader than Tier 1.
Full Suite
Edge + exception scenarios — full coverage. Run before releases or after major changes. Produces automation / manual / blocked / skip classified report.
Tier 3 full report — per-module automation rate · execution results · ambiguous / blocked / manual / skip classification.
You run it yourself when we're done.
Claude Code alone is enough — AI-readable docs + E2E guardrails as the safety net.
Locked in after handoff
Most agencies keep you on retainer even after handoff.
AI-readable Docs + E2E
CLAUDE.md / Skills let AI understand the system; E2E validates the golden path every time.
AI Usage Tracker
Our own tool deployed on client infrastructure. Full source public, zero external dependencies.
We measure and improve our AX every day.
We're the team that uses AI Usage Tracker to measure and improve our own team's AX daily. The system we built through AX — we ship it to you as-is.
AI Usage Tracker
The tool we use to measure and improve our own AX (AI Transformation) level every day. Team AI usage · efficiency · industry benchmarks — we look at these daily and decide what to do next. Built by us, used by us daily — and the AX experience we accumulated building it flows directly to your organization.
4+ years running Web3 dApps in production. Smart contracts · DEX · Bridge · Governance · Launchpad — full stack. IDO/INO token sale execution experience.
Progress you see week over week.
Scope + first working code
Requirements aligned · CLAUDE.md skeleton · one golden path working end-to-end.
Weekly demos + GitHub merges
Working demo every week. Priority retro · agree on next week's scope.
4 deliverables handed off
Code · Docs · E2E · Runbook fully handed over. No-lock-in wrap-up.
Requirements aligned · fit assessed.
See first-week results, then commit.
After 4-deliverable handoff, no forced retainer.