A demo at every sprint
During Build each sprint ends with a working demo, so you judge progress against the plan you agreed, sprint by sprint.
How we work
Listen first. Everything else follows.
The Path is how we run every engagement, from a website or an app to an automation or a security review. Five phases: Listen, Shape, Build, Launch and Evolve. It starts with your problem, never with a service to sell, and each phase ends with something you can hold. We refined it over 4+ years and 60+ projects.
You set the pace. We agree the schedule with you at the start.
PlanningBuilding and launchOngoing care
- Starts day one
Listen
A documented brief.
- Before any build
Shape
A technical plan, screen layouts and a scope you can hold us to.
- Built in sprints you can see
Build
A working demo at every sprint.
- When you are ready
Launch
Every source file, login and a recorded walkthrough.
- Ongoing
Evolve
A portal where every request and approval is on record.
Step by step
What happens in each phase?
Open a phase to see what happens, what you receive and how you are involved. The dates for your project go in the scope, agreed with you before any build starts.
Phase 1 of 5Starts day one
Listen
Why do we start by listening?
Before anything is designed, we listen: to the problem, to the people who live with it every day, and to the result that would make a real difference. You do not need to know yet whether the answer is a website, an app or an automation.
What happens
- A first conversation about the business: what is slowing it down, what you have tried, and what success would look like.
- Mapping how the work happens today, including the workarounds, and the moments where people get stuck.
- A look at your market and competitors, to see where you can stand out.
What you receive
- A documented brief, written down so nobody relies on memory
How you are involved. You tell us about the business in plain words. We ask a lot of questions, then send you the brief to check before anything else happens.
Phase 2 of 5Before any build
Shape
How does what we heard become a plan?
What we heard becomes a plan: what to build, how it will work, what it will look like and which technology suits it. Sometimes the plan is smaller than you expected. Most projects succeed or fail here, before a single screen is built.
What happens
- A technical plan that suits your size and the software you already use.
- Wireframes (rough screen layouts) and a map of how pages and information fit together.
- A scope with milestones, deliverables and review checkpoints.
What you receive
- The technical plan
- Wireframes and a page map
- A scope you can hold us to
How you are involved. You review the layouts and the scope, and we agree the schedule together before any build.
Phase 3 of 5Built in sprints you can see
Build
How do we build it?
Build is where the plan becomes the real thing: the website, app, automation or system we shaped together. Security and testing are part of it from the first sprint, and every piece is held to one standard, whatever the size of the project.
What happens
- Design rules first: fonts, colours, spacing and how things respond to a tap or click.
- Access control, security headers and careful handling of your data, built in from the start.
- Building in sprints (short blocks of work), each one ending in a working demo.
What you receive
- A working demo at every sprint
How you are involved. You see each demo and give feedback, so you judge progress against the plan.
Phase 4 of 5When you are ready
Launch
What do we check before go-live?
Before anything reaches your customers, we test it on real phones and browsers, and in awkward conditions such as a slow connection. Then everything is handed over.
What happens
- Testing on real devices as well as simulations, plus a speed check.
- Accessibility and edge cases worked through, with the results documented.
- Handover and written documentation.
What you receive
- Every source file
- Every login
- A recorded walkthrough
How you are involved. You decide when it goes live. Nothing depends on us to keep running.
Phase 5 of 5Ongoing
Evolve
What happens after launch?
Technology is never finished. We keep it updated, secure and measured as your business grows, and small changes get handled, not invoiced.
What happens
- Annual maintenance: updates, uptime checks, security fixes and speed tuning.
- Monthly tech partner retainers: ongoing development, strategy calls and priority support.
What you receive
- A portal where every request and approval is on record
- A way back into Listen when the business changes
How you are involved. You raise requests through the portal and see what was done and when.
After launch
Evolve leads back into Listen.
Your business keeps changing, so the technology behind it has to as well. When it does, the next cycle starts the way the first one did: by listening, this time with everything we have learned since.
- Annual maintenance covers updates, uptime checks, security fixes and speed tuning.
- Monthly tech partner retainers give you ongoing development, strategy calls and priority support.
- Small changes get handled, not invoiced, and every request is on record in one portal.
How we keep you informed
How will I know what is happening at each step?
One portal
After launch, every request, what we did and when sits in one portal you can see. Nothing lives only in someone’s inbox.
Direct access to the people doing the work
No account managers in between. Email, phone or WhatsApp the team building your project, and you never have to explain it twice.
- The first conversation ends with a written brief, not just meeting notes.
- The scope lists milestones, deliverables and review checkpoints.
- If something changes, we tell you as soon as we know, and agree any change to the scope with you first.
- If a request would not give you a good result, we say so before any invoice is raised.
In their words
Clear on paper first.
Founders we have worked with, on what it was like to work this way. Quoted exactly as they said it.
- Years in practice
- 4+
- Projects delivered
- 60+
- Industries served
- 15+
- Countries reached
- 3+
Questions about how we work
Do I need to know what I want built before we start?
No. That is what Listen is for. Tell us what is slowing the business down, and we work out together whether the answer is a website, an app, an automation or something smaller.
How long does a TechSum project take?
You set the pace. Listen starts on day one, and we agree the schedule with you before any build and put it in the scope. AI is built into how we work, so where the work allows it we move in days, not months.
Can I see progress during the build?
Yes. Build runs in sprints, and each one ends with a working demo, so you judge progress against the plan.
Do I get the source files and logins at the end?
Yes. At launch you receive every source file, every login and a recorded walkthrough. Nothing is withheld, and nothing depends on us to keep running.
What happens after the site or app goes live?
Evolve begins. We keep what we built updated, secure and measured through an annual maintenance contract or a monthly care retainer. When the business changes, Evolve leads back into Listen and the next cycle starts.
What if something changes halfway through?
We tell you as soon as we know, and we agree any change to the scope with you before it happens. If a request would not give you a good result, we say so before any invoice is raised.
Every engagement starts with listening
The first step is a conversation.
Tell us what is slowing your business down, in plain words, or book a short call. Not ready yet? Run a free health check on your site first.
Write whenever it suits you. A person on the team reads every message.
Write to us
Name and email are enough to start. “Not sure yet” is a fine answer.
Or book a short call
Pick a time that suits you. We talk about your business and what should change, and you leave with a sensible first step.
Loading the calendar.Open the booking page