Technology built around how the business works.
SFn designs connected digital systems across experience, software, operations, automation, data and customer workflows. The work begins with the operating model—not a predetermined product or stack.
Disconnected technology creates operational drag.
A website creates a lead. A CRM assigns it. A sales process qualifies it. Software delivers the work. Automation moves information. Data explains what happened.
When those layers are designed independently, staff compensate with spreadsheets, messages, duplicate entry and manual reconciliation. SFn works across the boundaries so the system behaves as one operating environment.
Show the system, not a list of claims.
SFn publishes internal systems and reference architectures openly. Client work is only presented when it is real and approved for publication.
SFn Consortium Digital Platform
The company website itself: a lightweight multi-page platform combining capability discovery, software search, industry mapping, guided scoping and a persistent project brief.
Read note ↗Internal systemSoftware System Explorer
A structured catalogue of business-system patterns designed to match plain-language operational problems to relevant software families and SFn capabilities.
Read note ↗Reference architectureClinic Operations System
A reference operating model showing how patient-facing experience, appointments, front desk, payments, follow-up and reporting can be designed as one connected system.
Read note ↗Nine practices. One operating view.
Each practice has its own methods and standards. They combine only when the business problem genuinely crosses boundaries.
The work between the boxes matters most.
A project can begin at any point. Architecture establishes what owns the data, where responsibility changes and how the system behaves when something fails.
Custom systems for workflows that no longer fit generic tools.
SFn models users, permissions, information, states and exceptions before designing interfaces. A structured System Explorer helps translate operating problems into relevant software patterns without pretending every business needs custom development.
- Lead & estimate
- Schedule & dispatch
- Technician workflow
- Parts & job status
- Invoice & maintenance
Start with the operating model.
Industry pages describe workflow patterns and common system breaks. They do not claim specialist credentials that have not been established.
From operating problem to controlled system.
Quality is part of the architecture.
Appropriate projects consider authentication, authorisation, validation, auditability, data constraints, failure states, accessibility, performance, observability and recovery from the beginning.
Engineering at SFn ↗Decisions before deliverables.
Short field notes on product, software and operating architecture.
When a spreadsheet should become software
The trigger is not row count. It is when the workflow needs permissions, state, history, validation or shared operational control.
AI agent or deterministic automation?
The most reliable architecture uses AI only for the parts that genuinely require interpretation, language or uncertain judgment.
Build, buy or integrate: the decision before the build
Custom software is valuable when the workflow is differentiating or poorly served. It is wasteful when a mature product already solves the requirement.
A founder-led technology company built around connected systems.
SFn is being built as a business technology company rather than a loose collection of agency services. The company is organised around research, architecture, design, engineering and continuous improvement.
It does not invent client proof, regulated credentials, scale or history. Credibility must come from the quality of the systems, methods and work that can be shown.
About SFn ↗Describe what the business needs to control, connect or improve.
A project can begin with a specific deliverable or an unclear operating problem. SFn will define the scope before committing to the build.