Solution sets · hubs and spokes

What keeps slowing your team down?

Four colleagues collaborating on a workflow diagram at an accessible office table
Build the program around the people and handoffs involved.Illustrative scene

Repeated questions. Training that does not stick. Missed follow-ups. Marketing that falls behind. Choose the work you need help with, and we’ll help shape the solution. Training, Admin, Agency and Sales support different jobs using one shared Brain built from your approved company knowledge. We show you the relevant workflow and agree on the complete scope together.

Bring one recurring problem and the people who handle it. We will work through the sources, actions, review points and handoffs involved.

One problem often crosses more than one department.

A new employee may need to learn an intake procedure, then use it when a website request arrives. A campaign may open a conversation that the sales team must prepare for and follow through on. When each program has separate knowledge and disconnected handoffs, the work between them falls back to people. The result is often unclear ownership, repeated explanations and decisions made without the same approved source.

The work, made clearer

Give the work a clearer path forward.

Start with the everyday problem. Then define the knowledge, actions and human responsibilities that make the program useful.

01

One shared foundation

Simpl Brain includes an employee-facing assistant, source-grounded answers with citations, instructions, guardrails and human handoff. The selected solution sets use that shared foundation, with access and responsibilities defined for each workflow.

02

Clear jobs for each hub

Training builds learning and practice. Admin connects requests to actions. Agency coordinates marketing. Sales supports preparation and follow-through. Each hub has a distinct role, scope and owner.

03

Capabilities where they belong

Voice, reporting, public website agents, video and connected-system work extend the appropriate workflow. Some capabilities belong to a hub; others are added and scoped in the proposal.

A workflow you can follow

Build a program around a request that keeps getting stuck.

Illustrative workflow: a new employee completes training on an approved intake procedure, then uses an Admin workflow when a public website request arrives. The request is captured, relevant source material is made available, and the next action is prepared for review. If the request needs sales follow-through, the Sales workflow can support preparation and a human owner completes the handoff. Your approved information, connected systems and review rules determine the actual implementation.

Your demo is a guided working conversation, not a package calculator. The proposal follows the agreed workflow and commercial scope, including included capabilities, added work and responsibilities.

  1. 1

    Identify the recurring problem

    Describe the trigger, the people involved and the final action that makes the job complete. For example: a new request arrives, a staff member needs the correct procedure, and an owner must decide what happens next.

  2. 2

    Establish the shared knowledge

    Confirm the approved source material, instructions and guardrails for the workflow. Identify the people responsible for reviewing and maintaining that knowledge in Simpl Brain.

  3. 3

    Choose the hubs and capabilities

    Use the role of each solution set to identify the needed learning, administration, marketing or sales work. Scope any public channel, voice capability, reporting, video or system connection separately where required.

  4. 4

    Set the review point

    Define what can be prepared from approved sources, what requires a person to check it and which actions remain with the responsible owner. Test representative cases before launch.

  5. 5

    Agree on the final handoff

    Document the deliverables, exceptions, destinations, review responsibilities and ongoing ownership in one proposal. The workflow is not complete until the responsible person knows what to do next.

Define the complete job, including the handoffs.

Your proposal identifies the included deliverables, channels, integration work, review points and ongoing responsibilities. One shared Simpl Brain supports the selected solution sets in your program.

Training

SimplTraining turns approved knowledge into curriculum, voice roleplay, a recurring learning path, reinforcement and basic completion visibility.

Admin

Admin connects requests to actions across email, calendars, notes and standard systems where the required access and supported actions are confirmed. A public website agent, voice channel or custom intake integration can be added when the process requires it.

Agency

SimplAgency coordinates campaign strategy, content and social operations, approvals and monthly reviews. Video, email, reporting and other campaign capabilities are scoped around the agreed plan.

Sales

SimplSales supports playbooks, discovery and objection practice, conversation intelligence, follow-up drafts and standard CRM activity sync when the required connection and scope are confirmed.

A project coordinator reviewing a paper task list in a shared workspace
People own the sources, the review and the decisions.Illustrative scene

People stay in control

The combination should have clear owners.

A shared knowledge foundation does not mean every person or public channel has the same access. Define the sources and actions appropriate to each workflow, identify reviewers and keep decisions with the people responsible for them. Automation should prepare useful work without obscuring who checks it or who owns the final action.

  • Use one Simpl Brain across the selected solution sets.
  • Identify included capabilities, conditional connections and added work in the proposal.
  • Separate employee, public-facing and sensitive workflows through explicit scope and access rules.
  • Keep source review, exceptions and consequential decisions with designated people.

Make the first implementation practical.

Begin with a useful workflow, confirm what the source material and connected systems support, and test representative cases before launching the agreed scope.

  1. 01

    Describe the job

    Show us a repeated question, intake request, training gap, campaign handoff or sales activity that creates unnecessary work.

  2. 02

    Map the trigger and destination

    Identify where the work starts, which approved sources inform it, what action is prepared, where a person reviews it and who receives the final handoff.

  3. 03

    Explore a relevant demo

    Review the proposed source use, actions, access rules and human decisions with the people who own the workflow.

  4. 04

    Confirm scope and connections

    Check system access, permissions, supported actions, deliverables, channels and responsibilities before implementation. Vendor compatibility is confirmed as part of this review rather than assumed from a name alone.

  5. 05

    Launch a useful starting point

    Start with the agreed workflow and representative cases. Expand when the next job has a clear purpose, owner and scope.

Before you book

Questions worth answering.

Understand the fit, the scope and the next step.

What is a solution set?

A solution set is a hub of related capabilities for a particular job. Training, Admin, Agency and Sales are the four hubs. They all run on one shared Simpl Brain.

What is a spoke or add-on?

A spoke extends a hub where the workflow needs an additional capability. A public website agent extends Admin, SimplVideo extends Agency, and reporting dashboards can serve multiple hubs. SimplVoice is a shared capability: roleplay is included in Training and Sales, while an Admin voice channel is separately scoped.

Do we need all four hubs?

No. Choose the solution sets needed for the work you want to improve. A demo helps establish a useful starting point, and the proposal identifies the combination and responsibilities.

Do we need another Simpl Brain when we add a hub?

No. The same Simpl Brain supports the selected solution sets. New sources, access rules or connections may still require configuration, which is identified in the proposal.

What happens to existing SimplAssist or SimplScribe programs?

SimplAssist is now the Admin solution set. SimplScribe is now SimplVoice, the shared voice and conversation-intelligence capability. An existing program’s signed scope remains the basis for discussing additions.

Where can we see pricing?

Pricing is discussed after we understand your goals and demonstrate the relevant workflow. Your proposal specifies the included work and commercial terms, with the engagement structured around a lasting partnership.

Can you work with the systems we already use?

We check available access, permissions and supported actions before agreeing to a connection. A vendor name alone does not establish compatibility for every workflow.

What remains with our team?

Your team provides or approves the relevant source material, identifies workflow owners, reviews proposed access and actions, and makes the decisions assigned to people in the agreed scope. The proposal records these responsibilities.

Built for a lasting partnership

Let’s show you how this fits your work.

Bring one recurring problem and the people who handle it. We will map the trigger, source, action, review point and final handoff, then scope the right combination with clear deliverables and responsibilities. We tailor the scope and price to your business, with competitive pricing designed for a lasting relationship.

A useful starting point is one recurring problem and the people who handle it. Book a demo to work through it together.