01
Web and cloud applications
Customer-facing platforms, SaaS products and secure browser-based tools.
Software services / Build
Create something new
Build the right product from the beginning.
Custom software shaped around the business problem, engineered for dependable use today and structured to support what comes next.
Discuss your build
Modular from day one Ready to extend without destabilising the core.
Who it is for
Founders and operations leads who need software that does not exist yet — a first product, or an internal system replacing a spreadsheet nobody trusts any more.
How it is sold
Fixed price against fixed deliverables once scope is agreed. Discovery is quoted separately, because pretending to fix a price on unknowns only produces padded quotes.
Start here
A paid discovery sprint: we map users, workflows and constraints, then hand you a scoped build plan you own whether or not we build it.
Book a discovery sprintWhat we can build
Software designed around the work it must do.
The build route covers new digital products and operational systems — from a focused first release to a platform intended to grow across teams, users and markets.
02
Mobile applications
Purpose-built mobile experiences for customers, employees and field teams.
03
Internal business systems
Workflow tools that replace fragmented spreadsheets, manual steps and duplicated work.
04
Portals and dashboards
Clear, role-based access to information, services, reporting and actions.
05
APIs and integrations
Connections between systems, services and third-party platforms without brittle workarounds.
06
MVPs and digital products
A focused first release that validates the idea without compromising the future foundation.
What is included
Everything between the idea and a system people can rely on.
Discovery and requirements
Users, workflows, constraints and success criteria.
Product and UI design
Journeys, prototypes, interface systems and implementation.
Solution architecture
Application structure, service boundaries and technical decisions.
Database and data design
Suitable models, access rules, migrations and future reporting needs.
Security and quality assurance
Reviews, automated tests and release checks throughout delivery.
Deployment and handover
Environments, documentation, source code and operational knowledge.
Built for what comes next
Expansion should not require starting over.
We plan for likely change early, so new users, modules, integrations and workloads can be introduced with less disruption to the core product.
- Modular architecture
Features are separated into clear components rather than one fragile block. - Stable data foundation
The data model supports current workflows and anticipated reporting needs. - Change-safe delivery
Version control, automated testing and controlled releases reduce avoidable risk. - Operational visibility
Logging and monitoring make performance and failures easier to understand.
Core experience
New modules
Core productStable foundation
Data and reporting
APIs and integrations
New capability attaches to the core instead of replacing it
A different delivery standard
The difference is what happens before launch.
A product can appear complete while carrying hidden constraints. We make the decisions behind the interface visible and deliberate.
| Decision area | Typical first build | PsalmTech build |
|---|---|---|
| Starting point | A supplied list of features | Business outcome, users and workflows |
| Architecture | Designed around the immediate release | Designed around the release and likely change |
| Quality | Testing concentrated near launch | Quality checks integrated throughout delivery |
| Documentation | Often treated as a final extra | Technical decisions and operations documented |
| Ownership | Knowledge remains with the builder | Source, knowledge and handover remain transferable |
The build engagement
From idea to operational software.
The sequence creates decision points early, keeps delivery visible and prepares the product for a controlled launch.
01
Discover
Needs, users and constraints.
02
Define
Scope and success criteria.
03
Design
Journeys and architecture.
04
Build
Working software in increments.
05
Assure
Testing, security and readiness.
06
Launch
Deployment and knowledge transfer.
What you receive
- Working software
- Source code
- Deployment setup
- Quality evidence
- Documentation
- Handover
Proof
A build that had to satisfy SARS, not just the client
10Bucksonly is a multi-tenant fundraising platform built from scratch: campaigns, donations through Ozow, a central donor database, and Section 18A certificates and IT3(d) files generated automatically from live data.
Ready to create something new?
Bring us the idea. Leave with a build direction.
Tell us what needs to change in the business, who the software must serve and what success should look like. We will help translate that into the right technical starting point.