Bring the problem.
A process, opportunity, existing system or early idea is enough to begin. Handspan helps work out whether software is the right answer and what should actually exist.
Good software starts with understanding.
Software,
at human scale.
A closer kind of software practice.
Handspan is a founder-led software practice in Cape Town. Bring a website need, a process, an existing system or an early idea; Handspan helps work out the right thing to build and carries it through properly. Small, contained projects are welcome. You work directly with the person doing the work.
Start a conversationA lighter way to work
The work should move
off your plate.
Bringing in technical help should not give you another supplier to explain to, chase and manage. Handspan keeps context close to the implementation and takes responsibility for carrying a useful outcome through.
Stay informed, not occupied.
Progress, trade-offs and decisions stay visible. You know where things stand and where your input matters without becoming the project manager.
Own what is built.
Bespoke work is documented and handed over properly. Once the agreed obligations are met, the aim is to leave you with the source code and context needed to understand and own it.
Capabilities
The right thing.
Built properly.
Not every problem needs a new platform. Sometimes it needs a small, well-made tool. Sometimes it needs a deeper rethink. The work starts by finding the right scale.
Websites & digital experiences
Websites that do their job properly.
A new business website, focused landing page or considered rebuild. Clear digital experiences that look right, make it easier for people to take the next step and are straightforward to own—connected to other systems where that is useful.
- Business websites
- Landing pages, forms & customer journeys
- Redesigns & existing-site improvements
- Performance & system connections
Applications & internal tools
Software that fits the work.
An internal tool, a data-backed application, a useful first version of a product, or focused work on something that already exists. Built around the people using it and the outcome it needs to create.
- Internal tools
- Data-backed applications
- Prototypes & MVPs
- Existing-product work
Systems & integrations
Systems that work together.
Connect the tools a business relies on and give information a clear path between them. Less re-keying, fewer fragile hand-offs, and failures that can be understood and resolved.
- APIs & backend services
- System integrations
- Event-driven software
- Reliable data flows
Automation & applied AI
Automation where it earns its place.
Remove repetitive work and awkward operational steps without automating for its own sake. AI is applied carefully when it solves a real problem, not used as a label for the project.
- Workflow automation
- Operational tooling
- Document & data workflows
- Carefully applied AI
Technical guidance & focused engineering help
A clearer way forward.
When a project is stuck, a system is becoming difficult to change, or the next decision matters. A close look at the problem, the constraints and a practical route forward.
- Discovery & scoping
- Architecture reviews
- Delivery decisions
- Focused engineering help
Engineering, through and through.
Current hands-on capabilities include TypeScript, Node.js, NestJS, PostgreSQL and AWS, alongside API design, event-driven software, integrations, automated testing and observability. Technology follows the problem; a new framework is not a reason to rebuild a working system.
Good-fit situations
Start with what is
getting in the way.
The common thread is not an industry. It is a contained, meaningful problem and value in having one accountable person carry it through.
Examples of possible starting points—not case studies.
A website that no longer represents the business.
A business needs a first website, or the current one is outdated, unclear or difficult to use. The aim is a credible, well-made experience that helps the right people take the next step.
Operations held together by hand.
Quoting, stock, production or service delivery lives across spreadsheets, WhatsApp and email, creating repeated work and avoidable uncertainty.
Systems that do not communicate.
Important information is copied between tools, arrives late, or disappears between teams because the connections are missing or unreliable.
An idea that needs a useful first version.
A founder or business has a worthwhile product idea but needs help deciding what to build first and carrying it into real use.
An existing application that needs focused work.
A contained feature, integration, reliability problem or architectural decision needs capable attention without turning into a larger programme.
Approach
From a real problem to software in use.
Progress stays visible and decisions stay close to the work. You should know what is happening and where your input matters without having to run the project. The amount of process scales to suit the work.
- 1
Understand
Look closely at the work, the people involved, the desired change and the constraints that matter.
- 2
Define
Agree on a useful outcome, a sensible scope, the risks and the trade-offs before committing to the shape of the work.
- 3
Design
Shape the flows, interface and technical approach while decisions are still inexpensive to change.
- 4
Build
Turn the plan into working software, shared early enough for useful feedback and tested as it grows.
- 5
Launch
Put the software into use deliberately, with the documentation, migration and preparation the situation calls for.
- 6
Stabilise
Watch how it behaves in real use, resolve the rough edges and confirm that the outcome is doing its job.
After stabilisation
Then close properly.
Once the software is stable, the work is handed over or any continuing support is agreed deliberately. The aim is to leave you able to own and understand what has been built.
The practice
Small on purpose.
Close to the work.
The person behind the practice.
Handspan is currently a one-person software practice. When you work with Handspan, you work directly with its founder—the person thinking through the problem and implementing the software.
The practice works across websites and digital experiences, backend systems, APIs, integrations, event-driven software, cloud infrastructure, testing and observability. Its focus is turning complicated operational problems into software that is understandable and useful.
Handspan is based in Cape Town, South Africa, and can work remotely. Projects are shaped around a useful outcome, the scope, the constraints and the trade-offs; the appropriate commercial structure can then be agreed.
See if it is a good fitTechnology should fit people.
Not the other way around.
A few useful things to know.
Do I need a finished brief?
No. Start with what you want to make possible, what is getting in the way, and any constraints already known. Handspan can help work out whether software is the right answer before deciding what to build.
What kinds of projects are a good fit?
Contained, meaningful problems where direct communication and technical accountability matter. That might be a business website, internal tool, integration, operational system, product first version, existing-application improvement or a difficult technical decision.
Can Handspan work with an existing team or codebase?
Yes. A focused piece of delivery, an integration or help with a technical decision can fit into an existing team. Responsibilities are agreed clearly, and the work respects the tools and practices that already serve the system well.
How does a project start?
With a straightforward conversation about the problem, the desired result and the surrounding constraints. If there is a sensible fit, the next step is shaped to suit the uncertainty—sometimes a short discovery, sometimes a clearly bounded scope.
What happens after launch?
Launch is followed by deliberate stabilisation. Once the software is working as intended, the project closes with a proper handover or any continuing support is agreed explicitly. Ongoing dependency is not treated as the default.
Who will I actually work with?
Handspan is currently a one-person practice. You work directly with its founder—the same person thinking through the problem and implementing the software.
Can Handspan bring in other specialists?
Handspan is currently founder-led, without an in-house team or a standing bench of contractors. If a project genuinely needs expertise outside the core capability, that need is identified and discussed openly before anyone else becomes involved.
Does Handspan only work with certain technologies?
No. Technology follows the problem and the existing environment. Current hands-on capabilities include TypeScript, Node.js, NestJS, PostgreSQL and AWS, but a new framework is not a reason to rebuild a working system.
Where is Handspan based?
Handspan is based in Cape Town, South Africa. The practice is South Africa-first and can work remotely, so a useful fit matters more than a particular city or industry.
Start a conversation
What would you
like to make better?
A small website need, a stubborn operational problem, an existing system that needs attention, an integration or an early idea. You do not need a finished brief to start.
Email Handspanhello@handspan.dev
Opens your email app. Just a conversation to begin with.