Process
How I work
From the first consult to delivery and handover — a 7-step process built around transparent decisions and dependable delivery.
- STEP 011–3 business days
Initial consult (30 min, free)
A free 30-minute online consult. I learn your problem, ideal outcome, and constraints (budget, schedule, existing systems), then give a first read on technical feasibility and a rough sketch of scope.
Deliverables
- 30-minute online consult (Google Meet / Zoom)
- First read on technical feasibility
- Recommended next step (requirements or direct estimate)
- STEP 021–4 weeks
Requirements definition (if needed)
Only when requirements aren't settled, a paid requirements phase. We lock down user stories, screen flows, API design, and the data model — which makes the subsequent estimate accurate.
Deliverables
- Requirements document (functional & non-functional)
- Screen-flow diagram & key wireframes
- Architecture diagram & key API specs
- Data model (ER diagram)
- Documented risks & assumptions
- STEP 031–2 weeks
Estimate & contract
A fixed estimate based on the requirements. We sign the contracts (master + individual), and handle the NDA here if it isn't already in place. Milestones, payment schedule, and acceptance criteria are all spelled out.
Deliverables
- Final estimate (fixed price, or hourly + cap for quasi-mandate)
- Master service agreement, individual contract, NDA
- Milestones & payment schedule
- Acceptance criteria (definition of done)
- STEP 041–4 weeks
High-level & detailed design
Finalize architecture, infrastructure, and API design in detail — Terraform module layout, CI/CD, and monitoring included — to a granularity that can be reviewed before implementation begins.
Deliverables
- Architecture design doc (component & sequence diagrams)
- Infrastructure diagram (AWS/GCP network & resources)
- API specs (OpenAPI)
- CI/CD pipeline design
- Monitoring & logging design, SLOs
- STEP 051–6 months
Implementation (2-week sprints)
Implementation and review demos repeat in two-week sprints. A demo at the end of each sprint drives a priority review. Code stays transparent through GitHub PRs.
Deliverables
- Demo every two weeks
- A working incremental build
- Per-PR code-review transparency
- Automated tests, lint, and vulnerability scanning (CI/CD)
- STEP 061–2 weeks
QA & security testing
Beyond unit and integration tests: manual QA, vulnerability scanning with OWASP ZAP, and load testing. Your acceptance-testing window is included here too.
Deliverables
- QA test report
- OWASP ZAP vulnerability scan results
- Load-test results (e.g. k6)
- Acceptance-testing support
- STEP 07Delivery → maintenance
Delivery & handover
After deploying to production, I provide a runbook, handover docs, and operating procedures. Optionally, we move to a maintenance contract for ongoing feature work and monitoring.
Deliverables
- Production deploy & smoke verification
- Runbook & operating procedures
- Up-to-date documentation & architecture diagrams
- Optional maintenance-contract proposal
Start with Step 1 — a free consult
“I get the process, but how would it play out for us?” I'll answer exactly that in a free 30-minute consult.