—Method
The 4-week process
A fixed framework. Projects of 4-8 weeks depending on complexity. Working software, not a 40-slide deck.
Week 1
Diagnosis
We map the real process, the SaaS tools you pay for and the pain points. We agree a fixed scope: what is in and what is out.
- Interviews with the people who run the process (not just management)
- Inventory of SaaS tools, costs and friction
- "Must have" vs "nice to have" list
- Signed scope document: deliverables, out of scope, definition of done
Outcome · A fixed, prioritised scope. No surprises in week 4.
Week 2
Infrastructure and ingestion
Server, database, pipelines and connectors. Your data stays in your infrastructure.
- Server / Docker / reverse proxy provisioning
- Database schema and backups
- Ingestion pipelines (documents, APIs, exports)
- Staging environment and secrets management
Outcome · Technical foundation ready. Data flowing into your system, not out of it.
Week 3
Agent / business logic
CRM, RAG or dashboard: the business logic, permissions and automations.
- Core build (pipeline, screens, agent)
- Permissions, roles and business rules
- Automations and reports
- Internal testing with real data, anonymised if needed
Outcome · A usable product in staging. Feedback from your team.
Week 4
Validation and deployment
Testing with your team, adjustments and go-live. Delivered with operational documentation.
- User acceptance testing with real users
- UX adjustments and critical edge cases
- Production deployment and smoke tests
- Runbooks, access handover and training session
Outcome · System in production. Your team can run it day to day.
Fixed scope from day one. No "we'll see as we go".
—Notes
- Simple projects: 4 weeks. Heavy integrations or several modules: up to 8.
- If the diagnosis shows a SaaS tool is enough, I will tell you. Four in ten calls end that way.
- No endless "discovery" phase. The scope is closed in week one.