Digital Systems Design
Strategic architecture for the websites, applications and workflows the organisation runs on. We design the system — and stay in the room while it’s built.
When organisations come to us for this
Four moments where Digital Systems Design tends to land:
A replatform on the horizon. A website rebuild, a CRM migration, a finance system replacement, a workflow overhaul. The vendor will be chosen soon, and the brief hasn’t been written by anyone senior enough to write it well.
A system estate that’s grown organically. Tools were added year by year as needs arose. Nobody designed the collection. Data sits in three places. The integrations are duct tape. The leadership team senses the cost without being able to name it.
A digital presence that’s drifting from the strategy. The website, the customer portal and the workflows around them were built for an organisation that’s since changed shape. They no longer say what the organisation now is.
Post-diagnostic, with systems flagged as the constraint. An Operational Intelligence assessment has surfaced that the application estate or the digital surface is what’s holding the organisation back. Now what?
What we design
Digital Systems Design is the strategic architecture work that sits between what the organisation needs and what the delivery partner builds. The scope flexes with the engagement, but the substance is consistent.
Current-state architecture.
A clear, leadership-readable map of the application estate, the workflows around it, the data flows, the integrations, the ownership and the cost.
Future-state architecture.
What the system should look like in two to three years’ time — source of truth, integration model, decommission list, investment sequence.
Workflow design.
The processes that run on top of the systems — who decides, who approves, what gets logged, what crosses systems, what stays manual on purpose.
Digital presence architecture.
Where the organisation shows up online — websites, customer portals, partner-facing applications — and how those surfaces connect to the systems behind them.
Vendor and partner brief.
The document the delivery partner gets handed. Specific enough to brief well, neutral enough not to predetermine the answer.
Architect-of-record during the build.
A senior advisor in the room as the delivery partner executes — holding the architecture to a standard, calling decisions early, keeping the leadership team informed.
What we do and don’t deliver: we design, architect and oversee. The build itself sits with your chosen delivery partner — your MSP, a specialist developer, a SaaS implementer, or a panel we help you assemble. Where the right partnership lines up, we can stay closely involved through implementation as the architect-of-record. As the firm grows, that side of the work is evolving — talk to us about what’s needed.
How it works
Most Digital Systems Design engagements run through four phases. The shape is consistent; the scale flexes with the size and complexity of the system being designed.
Discovery and current state.
Stakeholder mapping, application inventory, workflow walkthroughs, data-flow tracing. Documentation review where it exists, interviews where it doesn’t. The output is a current-state architecture that the leadership team and the technical team agree on.
Future-state design.
Target architecture, integration model, source-of-truth decisions, workflow redesign, presentation of options where there’s a real choice to make. Leadership-team review and sign-off on the direction.
Sequencing and brief.
What gets done first, what depends on what, what can be deferred. The vendor or delivery-partner brief. Selection support if needed.
Implementation oversight (optional).
Architect-of-record presence during the build — checkpoint reviews, vendor management, course-correction when reality diverges from design. Continues until the system is in production and the architecture is intact.
Total elapsed time: four to twelve weeks for design, plus the implementation window if oversight is in scope.
What you finish with
The deliverables are designed to be the briefing pack a delivery partner needs to do their best work — and the record the leadership team needs to hold the build to a standard.
- A current-state architecture document — readable by leadership, useful to the technical team and the delivery partner.
- A future-state architecture and integration design — the system as it should be in two to three years.
- A workflow design where workflows are in scope — process, authority and data flow, designed deliberately rather than inherited from whatever the previous vendor configured.
- A sequencing plan and vendor brief — the documents that let the build run from a strong foundation.
- Optional: an architect-of-record arrangement that carries through implementation.
Where Digital Systems Design fits
Digital Systems Design sits alongside the Operational Intelligence assessment and the Virtual CIO Service as a discrete engagement. It’s not a substitute for either.
After an Operational Intelligence assessment
When the prioritised actions point at systems and the answer is “redesign the architecture before the next investment.”
Inside a Virtual CIO Service engagement
When the retainer scope expands to include a major architectural piece, often a website rebuild or an application replacement.
As a standalone engagement
When an organisation already knows what’s coming up and wants senior architecture in front of it. No diagnostic needed first if the problem is well-defined.
The capability that underpins the work is Technology Architecture — the discipline that shows up inside other Farragan engagements when architecture is one of many factors. Digital Systems Design is what that discipline looks like when the architecture is the engagement.
Where we sit alongside your delivery partners
Designing the system isn’t the same as building it. Most of our clients work with a delivery partner — an MSP, a specialist agency, a SaaS implementer, an internal team — who’ll execute the build. We work alongside them.
The model is architecture-first. The design and the brief come from us. The build comes from them. We stay in the room during implementation as the architect-of-record, holding the design to a standard and surfacing decisions before they become problems.
As the firm grows, we’re evolving how closely we stay involved during delivery — including in some cases where the right partnership makes sense. Worth a conversation if delivery is part of what you’re thinking about.
Common questions
Do you build the website / application yourselves?
Not as a rule, today. We design and architect; your delivery partner builds. Where the right partnership lines up, we can stay closely involved through implementation. This is an area of the firm that’s evolving — talk to us.
Do we need to have a delivery partner picked first?
No. We can run the design engagement before the partner is chosen, and the brief that comes out of it is what helps you select well. If you’ve already picked a partner, we can still design — and we’ll work with them through the build.
Can you recommend a delivery partner?
We can point at partners we know and trust for specific kinds of work. We don’t take referral fees, and we’re not anyone’s sales channel. The recommendation is information, not a kickback arrangement.
How long does a Digital Systems Design engagement take?
Four to twelve weeks for the design itself, depending on scope. Implementation oversight runs alongside the build, which is usually three to twelve months on top.
Do we need an Operational Intelligence assessment first?
No, but it often helps. If the problem is well-defined (“we’re replatforming our CRM and need the architecture right”), Digital Systems Design can run on its own. If you’re not sure where the problem is, the assessment is the better front door.
What’s the relationship to the Virtual CIO Service?
A Virtual CIO Service engagement is ongoing senior advisory. Digital Systems Design is a discrete project with deliverables. Some clients run both — vCIO for the broader relationship, DSD for the architectural piece. Others run DSD as a one-off.
Book a 30-minute discovery call
We’ll talk through what’s coming up, where the design work needs to land, and whether this is the right shape.
Book a discovery call