Skip to content
Work/Business-development systems
SalesOS

Building SalesOS around the real work of business development.

Saxon Bridge's own company-centred system for organising prospect research, commercial context, outreach preparation and next actions—developed around the decisions that business development requires.

Systems
SalesOS by Saxon Bridge brand identity.

In-house system

Project type

Today → Company → Action

Core workflow

AI-assisted, owner-controlled

Approach

Ongoing development

Status

The operational brief

The brief was not to accumulate more leads. It was to keep knowledge about a company connected to an appropriate commercial decision: whether the evidence suggested a relevant need, which form of approach made sense and what should happen next. Research, company information, proposed work, preparation, review and follow-up therefore had to behave as one connected working structure rather than separate administrative tasks.

Charlie Sansom provides founder-led commercial and product direction: defining the practical requirements, shaping the company-centred workflow and judging the system against the business-development work it is intended to support. This account does not invent a wider team, a start date or a claim that Charlie personally hand-coded every element.

01

Why the company became the organising record.

The problem
A contact list can show names and addresses without explaining the commercial relationship. Research may sit in one place, notes in another and proposed work somewhere else. As soon as several people or possible projects are involved, the operator has to reconstruct the story before making a sensible decision.
The design decision
SalesOS places the company at the centre. Contacts, evidence, active commercial work, proposed approaches, activity and the next action contribute to one relationship context. The interface is therefore organised around the entity the business is trying to understand, not around whichever tool produced the latest item.
The artefact

The current company-workspace structure supports contacts, contextual information, active work, approval context and the primary next action together.

Actual interface with fictional demonstration data. The capture shows how company context and the current next action share one record; it is not a customer result.
Intended consequence
Before a call, proposal review or follow-up, the operator can inspect the reason for the opportunity and the most recent activity without rebuilding the context from disconnected records.
Qualification
The working demonstration shows the interface structure with fictional records. It does not establish production data quality, multi-user reliability or a customer outcome.
02

Why a focused Today view sits beside the full relationship context.

The problem
A complete database can contain everything and still be a poor place to start the day. Long pipelines and broad task lists make urgent decisions, awaited replies and exceptions compete with work that does not need attention now.
The design decision
The design uses a bounded Today surface as an entry point. It presents a manageable set of owner actions, while the company workspace retains the detail behind each item. Selecting the work should lead back to its relationship context rather than encouraging a context-free tick-box action.
The artefact

The working demonstration returned four fictional owner actions within a deliberately bounded Today view.

Actual interface with fictional demonstration data. It shows a starting point for judgement, not evidence that the displayed work completes automatically.
Intended consequence
The operator receives a clearer starting point, then opens the relevant company before deciding. This supports prioritisation without pretending that everything displayed will be completed automatically.
Qualification
The Today capture comes from the present interface running with fictional records and no live-provider access. It establishes visible structure, not production operation.
03

Why a research finding is not automatically a qualified opportunity.

The problem
Research can identify a gap, change or uncertainty, but those observations do not prove that a company intends to buy, has the relevant budget or regards the issue as a priority. Treating every finding as a qualified lead would make the pipeline look certain while weakening the judgement behind it.
The design decision
Research is presented as evidence for review. A finding can retain its source, confidence or uncertainty and a possible service need without becoming a buying signal by default. Qualification is a later commercial decision made in the company context.
The artefact
The demonstration returned illustrative research records with explicit evidence and uncertainty labels. They were fictional and were not presented as current research about a real organisation.
Intended consequence
A possible need can inform a fair, relevant question or justify further research. The operator can also decide that the evidence is too weak and record no opportunity.
Qualification
No live research provider has been established. The demonstration supports the way findings can be organised and reviewed, not a claim of automatic or current market research.
04

Why different approaches require preparation and review before external action.

The problem
A short pitch, detailed proposal and visual concept serve different commercial purposes. If they are generated or stored without the identified need beside them, output can become generic, overconfident or detached from what the company may actually require.
The design decision
SalesOS connects preparation to the company and the possible opportunity. The operator can compare the evidence, proposed work and chosen artefact, then review relevance, wording and scope. Approval of the copy remains distinct from any separately authorised provider action.
The artefact

The current interface includes company-linked preparation and draft-review areas. Fictional items remain visibly awaiting a decision.

Actual interface with fictional demonstration data. The review queue shows the wording, proposed work and status before any separately authorised external action; nothing was sent during capture.
Intended consequence
Commercial material has a visible reason to exist and a deliberate review point. An unsuitable draft can be edited, rejected or held while more evidence is gathered.
Qualification
A seeded artefact proves that the interface can present the item. It does not prove successful generation. No live email draft creation, provider synchronisation or sending was exercised.
05

Why follow-up—and any supported handover—stays attached to the relationship.

The problem
A good conversation can still disappear if the next step is stored as a detached reminder. The risk becomes greater when a proposal needs review, another person must continue the work or the commercial state is described imprecisely.
The design decision
A dated follow-up belongs to the company record and can return to the operator's Today view. Where later delivery handover is supported, the accepted work should retain enough company and proposal context for the next person to understand what was agreed.
The artefact

A fictional dated follow-up is returned with its company and service context.

Actual interface with fictional demonstration data. The overdue state is illustrative, not a real missed customer action; persistence and provider behaviour have not been established.
Intended consequence
The next action remains explainable when it reappears. The design also allows estimated opportunity value, accepted work and money received to remain conceptually separate rather than collapsing them into one optimistic status.
Qualification
The demonstrated follow-up is not evidence of durable production writes, a live delivery integration, a production audit trail or an end-to-end handover.
Artefacts and evidence

Classify what the evidence actually shows.

Actual interface with fictional demonstration data. The visible package is seeded: it demonstrates presentation and review, not that generation completed successfully.

Preparation is not generation proof

The interface distinguishes a concept, a pitch and a fuller pursuit package. The seeded sample shows where work can be inspected without being presented as provider or end-to-end generation evidence.

What is demonstrated

Working structure, not a published result

The interface captures show Today, the company workspace, preparation, review and follow-up using fictional records. They establish interface structure and deliberate review points; they do not establish customer adoption, provider reliability or measured business results.

Illustrative outputs

Display is not generation proof

A loaded concept or draft can show the presentation and review structure. Unless the generating action and provider behaviour are separately exercised, the item remains an illustrative sample rather than evidence of successful end-to-end production.

Outcome evidence

Scope and decisions—not invented performance

The demonstrable outcome is a connected product structure shaped around commercial decisions. No claim is made here about revenue, conversion, time saved, adoption volume or production uptime.

Iterative development

Refining the owner journey without pretending the product is finished.

The working demonstration brings the Today view, company context, illustrative research, loaded preparation, draft review and a dated follow-up into one owner journey. That breadth shows continuing refinement around navigation, action clarity, review points and the exceptions encountered in business development.

The demonstrated journey is useful development evidence, but it is not a substitute for production operation. Live-provider behaviour, scheduled work, persistent database writes, authentication boundaries and deployment reliability have not been established. The status remains in-house product · ongoing development.

Outcome

SalesOS now expresses a demonstrable product scope and a set of deliberate design decisions: company context as the organising record, a focused Today entry point, research separated from qualification, preparation separated from permission and next actions returned to the relationship. That is the evidenced outcome at this stage.

No measured increase in revenue, conversion or time saved is attributed to the system. Suitability for another business would require its own requirements and implementation assessment.

Discuss your system

Make your next action clearer.

Tell us how customer information, responsibilities and commercial work move through your business.