SFTech
Software engineering. Designs, implements, and delivers the solution to specification. Clean handover, documented intent, warranty period.
Custom software · Engineered for operations
Systems engineered
to operational-grade standards.
“We engineer the systems that run the business.”
SFTech designs, builds, and delivers custom software for enterprise and government-adjacent organisations. Every system we ship is architected for longevity, built for scale, and delivered ready to run.
§ A01About the firm
A specialist engineering firm, not a development shop.
SFTech builds custom software for organisations that need the system to still be in service a decade from commissioning. Architecture, code, and delivery discipline held to the standards of the team that will run it.
Most enterprise software is built to a demo, not to a decade. It passes acceptance testing, ships, and then slowly becomes the single largest liability in the business. Undocumented conventions. Unobservable internals. Runbooks that do not exist. By the time anyone notices, the original team has moved on.
SFTech engineers against a different target. We design every system with the assumption that a named operations team will run it for ten years, through staff turnover, regulatory change, and load we have not yet imagined. That changes what we build, how we document it, and what "done" means.
Our engineers are senior. Our architecture decisions are written down. Our handovers are rehearsed. When a system leaves our hands, it arrives with the runbooks, observability, and institutional memory required to keep running without us.
§ A01.2 · Partnership model
SFTech builds it.
FUSE DYNAMICS runs it.
A vertically integrated build-and-run model. SFTech engineers the software to specification. FUSE DYNAMICS, our operations partner, assumes long-term operational custody of it. Two disciplines, one accountable relationship.
FUSE DYNAMICS
Operational custody. Takes the delivered system and runs it for the long term across four pillars: manage, operate, protect, run.
§ A02Our disciplines
Four disciplines of engineering custody.
The spine of every engagement. Each discipline has a defined scope, measurable outputs, and a named engineer accountable for its delivery.
D / 01ARC
Architect
System architecture, technical design, and technology selection. The decisions that determine what is easy and what is impossible for the next ten years.
- Architecture decision records
- Technology selection
- Integration & data design
- Non-functional requirements
D / 02BLD
Build
Custom software development, systems engineering, and integration. Senior engineers working against a written design, reviewed on every change.
- Backend & services
- Web & internal tooling
- Integration & pipelines
- Infrastructure as code
D / 03ASR
Assure
Quality assurance, automated testing, and security review. Built into the engineering process, not bolted on before acceptance.
- Automated test coverage
- Security review & threat modelling
- Performance & load testing
- POPIA & regulatory review
D / 04DLV
Deliver
Handover, documentation, and operational readiness. The step most firms treat as administrative. For us, it is an engineering discipline.
- Runbooks & operational guides
- Observability & telemetry
- Architecture documentation
- Rehearsed handover to operations
Engineering standards
Engineered for the team that will run it.
Operational custody is not a final deliverable. It is a constraint applied from the first architectural decision. Four standards every SFTech system ships against, whether it will be run by FUSE DYNAMICS, an internal operations team, or a third party.
-
01
Runbook-first delivery.
Operational runbooks are authored alongside the code, not after acceptance. If a procedure is not written down, the feature is not complete.
-
02
Observability as a contract.
Logs, metrics, traces, and health checks are specified in the architecture and verified on delivery. The operations team inherits signal, not guesswork.
-
03
Architecture decisions recorded.
Every non-trivial decision is captured as a written ADR, with context and alternatives considered. The next engineer knows why, not just what.
-
04
Rehearsed handover.
A structured handover to the operations team: runbook walk-through, incident drill, and a signed readiness statement before code leaves our custody.
§ A03Why SFTech
Built for systems that have to last.
Four reasons customers retain us, plus the capability strip that procurement, risk, and engineering leadership most often need confirmed before they proceed.
D / 01
Operational-grade engineering
Every system we build is designed to be run at scale. Not just demoed, not just passed through acceptance. Engineered for the long tail of production.
D / 02
Built-in handover discipline
Documentation, runbooks, and observability are first-class engineering deliverables. Not an afterthought, not an add-on line item.
D / 03
Enterprise- and government-grade credibility
POPIA-aligned, built for regulated environments, South African jurisdiction. Engagement documentation stands up to procurement review.
D / 04
FUSE DYNAMICS partnership
Take the operational layer off the table entirely. Our sister operations company assumes long-term custody of the systems we build for you.
Posture
POPIA-aligned
Jurisdiction
Republic of South Africa
Run partner
Domicile
Centurion · Gauteng
§ A04Commission a system
Open a direct engineering channel.
Send us a clear brief: the problem, the systems in play, and the operational posture required. We respond within one business day with a discovery call and a short written return.
Email
Primary channel for scoping, procurement, and engineering enquiries.
Location
Centurion, Gauteng
Republic of South Africa · sftech.co.za
Response
Within one business day
Acknowledgement, discovery call, and written return, in that order.
Run partner
Long-term operational custody of commissioned systems, on request.
What happens next
T+0
Discovery
Acknowledged within one business day. Named principal engineer assigned. Scoping call scheduled.
T+14d
Architecture
Written architecture, technology selection, and non-functional requirements, presented and signed off.
Build
Engineering
Senior engineers working against the design. ADRs captured. Runbooks and observability written alongside the code.
Handover
Delivery
Rehearsed handover: runbook walk-through, incident drill, signed readiness statement, warranty period.
Run
Custody · FUSE DYNAMICS
Optional. Long-term operational custody assumed by our sister operations company, under documented SLAs.