We begin with a short discovery session to confirm your goals, target users, and success metrics. This can be a quick Zoom or Teams call, a phone conversation, or even async email exchanges. The outcome is a scoped project brief with agreed deliverables, timelines, and acceptance criteria — so everyone knows what success looks like.
Next, we consolidate all materials — product demos, SME input, repositories, brand assets, and top support tickets — into a single source of truth. This kickoff ensures requirements are locked and expectations are aligned, reducing scope creep and creating a clear governance baseline for the sprint.
Before drafting begins, we create a High-Level Design (HLD) document that outlines the scope, audience, format, tone, and deliverables. For video or e-learning, this includes a script or storyboard. For documentation, this includes an outline and structure. This checkpoint gives you full visibility upfront, so there are no surprises later.
The build happens in an Agile sprint cycle. Draft deliverables may include Quickstart guides, setup instructions, FAQs, API references, explainer scripts, or module storyboards — depending on scope. Communication remains flexible (email, Loom updates, or calls), while weekly sprint reviews ensure transparency and momentum.
Clients receive two structured review windows, each capped at 48 hours, with feedback collected in comments or tracked edits. Every item is addressed, risks are highlighted, and missing inputs are called out. This stage functions as a formal quality assurance checkpoint before sign-off. Any reviews beyond the two windows will be an additional charge.
Final deliverables are provided with a handoff playbook for adoption. Depending on your package, this may include docs, Swagger/Redoc embeds, Postman collections, or video exports. After launch, you can choose a knowledge base retainer for ongoing updates, analytics, and iterative improvements.
Joshua designed and built a full-stack app that streamlined our internal workflow and saved our team countless hours each week. He met with us consistently, incorporated feedback quickly, and delivered a solution that immediately made our staff’s day-to-day easier.
We went from having zero documentation to a complete help center guide. Joshua made our platform instantly more approachable for new users, and his clear structure has already cut down on repetitive support questions
Lite → Best for early-stage startups and seed companies. It’s the leanest option — a few core guides + FAQs — cheap, fast, and enough to help your first users get going without blowing budget.
Growth → Most popular with Series A/B teams. You get a professional doc set plus a polished explainer video. It’s the “smart middle” package — more impact, still a fraction of agency cost.
Ultimate → Designed for Series C and enterprise teams. Combines docs, video, and an e-learning module into one full enablement system. It’s for companies ready to scale onboarding across big teams and customers.
If you’re unsure, most startups or growing companies pick either Lite or Growth first and upgrade later.
Sometimes — but my focus is on documentation-first packages, since clear docs are the foundation of every good onboarding and training system. If you already have docs covered and just need a single add-on, I do offer:
Explainer video (60–120s): starts at $1.5-2k.
E-learning module (Storyline/Rise): starts at $3-5k
These are scoped as one-offs with clear deliverables, timeline, and two review rounds. If you need multiple explainers or a module series, I’ll create a custom package.
We’ll need a sandbox/demo environment, a seeded dataset, one admin login, and a non-production API key. A short walkthrough (20–30 min) and your brand kit will help us align on tone and visuals.
Each project is split into four equal milestones (25% each). Typical timelines are:
Lite → ~2–4 weeks
Growth → ~3-5 weeks
Ultimate → ~5–8 weeks or more depending on scope.
We assume timely access and feedback. Work pauses if invoices are overdue; dates adjust in writing.
We’re happy to sign a mutual NDA. Only demo/sandbox data is used (no production PII/PHI). On final payment, all deliverables are yours. I retain my underlying templates and methods but grant you a royalty-free license for any embedded elements.
