SalesOS by Saxon Bridge

Give every sales opportunity a clear next move.

Business development involves more than keeping a list of contacts. You need to understand the company, decide whether there is a relevant opportunity, prepare the right approach and remember what happens next. SalesOS is being developed to keep that work connected, with the company at the centre and the important decisions under your control.

In-house product by Saxon Bridge · Ongoing development

Discuss SalesOS See how it works

SalesOS company workspace for fictional Demo Services A, showing its stage, relationship, potential value, current next action and primary contact. — Actual SalesOS interface from an isolated demonstration using fictional records. It shows the company context and current next action together; it is not a customer result.

Guided product tour

From today's work to the next commercial decision.

The tour follows one practical thread: an operator starts with the work needing attention, opens the company behind it, tests whether there is a credible reason to approach, prepares suitable material, reviews it and records what should happen next.

Know where to start today.

The Today view is designed around owner actions: work that needs a decision now, replies that are waiting for attention and exceptions that should not disappear into a long pipeline. Selecting an item is meant to open the relevant company context, so the operator can understand why it is there rather than treating the task as an isolated reminder.

The useful distinction is between work visible today and all work in the system. SalesOS can present a focused starting view while the company workspace retains the fuller relationship history.

SalesOS Today view with fictional Demo Services owner actions, recent activity and company counts. — The Today view presents owner actions and recent company activity. All names and values are fictional demonstration data; no task was completed or sent during capture.

Recognisable task: Decide which action, reply or exception deserves attention first.
What the operator does: Open a bounded Today item, then move into the company record behind it before acting.
Practical relevance: The day begins with a decision-ready list instead of another undifferentiated database view.

The working demonstration supports a bounded Today view. It is a starting point for judgement, not evidence that every action completes automatically.

Keep the relationship—not just the contact details.

A company can involve several contacts, more than one possible project and different reasons for speaking. The company workspace is intended to keep those pieces together: who is involved, what is known, what work is active, what has already happened and which next action has been chosen.

This matters before a call or proposal review. The operator should be able to see the evidence behind the opportunity and the latest activity without reconstructing the relationship from an inbox, a spreadsheet and personal notes.

SalesOS company workspace for fictional Demo Services A, combining company context, current next action and primary contact. — The operator can see the fictional company’s stage, relationship, current next action and primary contact before opening the fuller work history.

Recognisable task: Prepare for a conversation with a company that has several people, possible projects and prior activity.
What the operator does: Review the organisation, contacts, research, active work, earlier activity and the recorded next step together.
Practical relevance: The operator can rebuild the commercial story from one organising record instead of separate notes.

The company workspace is shown with fictional demonstration records. It establishes the interface structure, not production data quality or a customer outcome.

Find a relevant reason for the conversation.

Research is useful only when it can be examined. A finding should retain enough evidence for the operator to understand where it came from, what remains uncertain and whether it suggests a possible need. For example, a hypothetical business may have unclear service information on its website. That can justify a closer look; it does not prove that the business wants a redesign or has budget available.

SalesOS is designed to keep that distinction visible. A possible need can inform a relevant question or approach, while qualification remains a separate commercial decision.

SalesOS intelligence view showing evidence freshness, company scope, sources, findings and uncertainty for a fictional company. — The intelligence view separates freshness, sources, findings and uncertainty. The displayed requirements are fictional; the capture does not prove automatic or current external research.

Recognisable task: Assess a hypothetical company whose website does not make an important service or route to enquiry clear.
What the operator does: Record the source, the finding, the confidence or uncertainty and a possible service need for review.
Practical relevance: The approach can be based on a specific observed gap while preserving the difference between a clue and buying intention.

The research shown in the demonstration is illustrative. It is not current research about a real company or proof of live automated research.

Prepare the right approach for the opportunity.

Different opportunities call for different forms of preparation. A concise pitch can open a conversation; a proposal can define agreed work; a visual concept may help someone understand a possible direction. Those outputs are not interchangeable, and each should trace back to the need that prompted it.

The design therefore places preparation within the company record. The operator can compare the evidence, proposed work and material being prepared before deciding whether it is relevant enough to continue.

SalesOS preparation workspace for fictional Demo Services B, showing concept, pitch and pursuit-package controls beside a seeded sample package. — The controls distinguish a concept, a pitch and a fuller pursuit package. The visible package is seeded demonstration content: its presence proves display and review structure, not successful generation.

Recognisable task: Choose whether the next useful artefact is a focused pitch, a proposal or a visual concept.
What the operator does: Connect the identified need to the proposed work, then prepare material in the same company context for review.
Practical relevance: The artefact has a reason to exist: it responds to a particular opportunity rather than becoming generic output.

The current demonstration can display company-linked preparation and a preloaded illustrative concept. That establishes presentation only; generation and provider reliability have not been established.

Review the approach before it leaves the business.

Review is not a ceremonial step. The operator needs to ask whether the wording reflects the evidence, whether the proposed work fits the situation and whether the message makes a fair claim. A draft may be edited, rejected or held for more research.

SalesOS separates preparation, approval of the content and any separately authorised external action. That keeps a useful human checkpoint without turning this page into a promise that a connected provider has sent or delivered anything.

SalesOS approvals view showing fictional outreach and creative work awaiting human review. — The approvals view keeps the visible recipient, wording, proposed work and consequence available for a person to check. Names and values are fictional; no message was sent during capture.

Recognisable task: Check a prepared draft or commercial artefact before any external step.
What the operator does: Review the evidence, relevance, wording and proposed work; edit or reject the content where the supported interface permits.
Practical relevance: Copy approval becomes a deliberate commercial review rather than an assumed instruction to send.

The demonstration includes fictional drafts in a review structure. No provider delivery, synchronisation or automated sending has been established.

Keep the next step attached to the relationship.

A useful next step may be a call, a proposal review, further research or a conscious decision to stop. Recording it against the company means the reason for the action remains available when it returns to the Today view.

If work is later accepted, the system design can support a handover into delivery context, but commercial states must stay precise. An estimated opportunity value is not accepted work, and accepted work is not the same as money received.

SalesOS Pursuits view showing a dated follow-up attached to fictional Demo Services H and its booking and conversion opportunity. — The fictional pursuit retains its dated follow-up with the company and service context. The overdue state is demonstration data, not a real missed customer action or evidence of durable production writes.

Recognisable task: Record the call, proposal review, dated follow-up or decision not to proceed.
What the operator does: Attach the chosen action and date to the company so it returns with the relationship context.
Practical relevance: The next decision remains visible without confusing a forecast value, accepted work and money received.

A dated follow-up is demonstrated, but durable production writes have not been established. Post-acceptance handover and external integrations require separate assessment and evidence.

Intended fit

For relationship-led work where context changes the approach.

The approach may be relevant to founder-led businesses, agencies, consultancies and relationship-led B2B teams. These are potential applications, not a list of existing SalesOS customers.

A conversation about fit would establish the operating process, the information that needs to be trusted, the users and responsibilities involved, any integrations, the support model and the point at which an external action may occur. Suitability and implementation cannot be assumed from the interface alone.

Process

How an opportunity moves from research to a decision.

Data

Which company, contact and activity records matter.

People

Who prepares, reviews, owns and acts.

Connections

Which providers or existing systems require scoped access and testing.

Availability and evidence

A current product direction, with important work still being established.

SalesOS is Saxon Bridge's in-house product in ongoing development. The working demonstration covers the company-centred structure, Today actions, evidence and uncertainty, company-linked preparation, draft review and dated next actions.

The interface captures on this page come from the present interface running in an isolated demonstration with fictional records and no live-provider access. They establish visible interface structure and review points. Production reliability, automated completion, external-provider behaviour and commercial outcomes have not been established.

Read the development case study →Explore bespoke CRM work →

FAQs

Common questions

Is SalesOS available as a self-service product?: Not at present. SalesOS is an in-house Saxon Bridge product in ongoing development. The current route is a conversation about fit, workflow and implementation rather than instant registration, a free trial or a published price plan.
Does the system replace commercial judgement?: No. The system is intended to keep evidence, preparation and next actions connected. A person still decides whether an opportunity is relevant, whether the proposed approach is appropriate and whether any external action should be authorised.
Can it be adapted to another business?: Possibly, but suitability depends on the process, records, users, integrations, access requirements and support model. A bespoke client system begins with those requirements; it is not assumed to be a copy of SalesOS.

Next step

What should your next sales action be?

Tell us how you currently research companies, prepare approaches, review decisions and follow up. We can discuss whether the SalesOS direction—or a separately scoped system—fits the work that needs to be done.

Discuss SalesOS