How we weave
Five motions. No surprises.
A hand loom has five motions, repeated in order, for as long as there is cloth to weave. Our projects work the same way: a predictable rhythm, every step visible, and working software every week.
01 · Let-off
Discover & Architect
The warp is released and set under even tension.
Usually 2 weeks
We learn your business, your users and your constraints, then design the structure everything else will hang on. You leave with a plan you could build with anyone (though we hope it's us).
What happens
- Stakeholder & user interviews
- Domain and data modeling
- Architecture & risk review
- Scope, milestones and estimate
You get
Problem map, architecture, estimate
From you
Two or three working sessions, access to the people who know the problem.
02 · Shedding
Shape & Design
Chosen warp threads are lifted to open a path.
2 to 4 weeks, overlapping the build
We decide what goes into the first release and what waits. Flows and interfaces are designed, prototyped and tested with real users before engineers commit to them.
What happens
- User flows & wireframes
- Interface design
- Clickable prototype
- Usability testing
You get
Scope, UX/UI, clickable prototype
From you
Weekly design reviews and quick decisions on trade-offs.
03 · Picking
Build in passes
The shuttle carries the weft across, pass after pass.
The bulk of the project
Working software in thin, complete slices. Every pass is reviewed, tested and deployed to a preview you can click through, so progress is something you use, not something you're told about.
What happens
- Weekly demo on a live preview
- Shared board: every task visible
- Code review on every change
- Continuous deployment
You get
1 to 2 week sprints, weekly demos
From you
A weekly 45-minute demo, and feedback within a day or two.
04 · Beating-up
Harden
The reed packs each new thread tight against the cloth.
Built into every pass, plus a final week
Each new thread is packed tight before the next goes in. Automated tests, security checks, accessibility and performance budgets run continuously, with a dedicated hardening pass before launch.
What happens
- Automated test suites
- Security & dependency review
- Accessibility (WCAG 2.2 AA)
- Load & performance testing
You get
QA automation, security, performance
From you
User acceptance testing on the release candidate.
05 · Take-up
Launch & Evolve
Finished cloth rolls forward onto the beam.
Launch week, then ongoing
A rehearsed launch, monitoring from minute one, and a clear choice for what comes next: we keep weaving on a care plan, or we hand your team the loom with documentation and training.
What happens
- Rehearsed, reversible release
- Monitoring & alerting
- Runbooks and documentation
- Care plan or full handover
You get
Release, monitoring, care plan
From you
Go/no-go decision and a say in what's woven next.
Every thread accounted for.
Weekly demo
Every week, working software on a live preview link. Never slides.
Shared board
Every task, decision and blocker visible to you in real time.
Written updates
A short async summary each week: done, next, risks, decisions needed.
Time-zone overlap
Mornings with the US East Coast, afternoons with the UK and Europe, all day with the Gulf and Asia-Pacific.
What “done” means here
Nothing is called finished until it meets all six. It’s the reed that packs each thread tight.
- 01Reviewed by a second engineer
- 02Covered by automated tests
- 03Accessible by keyboard and screen reader
- 04Within the agreed performance budget
- 05Deployed to a preview you can try
- 06Documented where the next person will look
You own every thread.
Code, designs, documentation and infrastructure live in your accounts from day one, and the intellectual property is assigned to you as work is paid for.
No proprietary frameworks, no hostage-ware. If you ever want to continue without us, you can, and we’ll help you do it well.