Source One Second Brain

Option	What it is	Ballpark cost	Verdict
Wiki / knowledge platform Notion, Guru, Confluence	Structured pages, search, permission tiers, templates, version history. Notion fits a company Source One's size; Guru adds automatic "re-verify this stale article" workflows if we outgrow Notion.	~$10–18 / user / month	Start here Running in a week, no developers
AI layer on our docs Claude Enterprise, Notion AI, Guru AI	The "company-specific LLM." The modern approach is retrieval, not training: the AI searches our knowledge base and answers with citations — "What do I do if a worker no-shows in Illinois?" → the answer, linked to the SOP. Our data stays private; nothing trains on it.	~$25–30 / user / month for the AI tier	Phase 3 Only as good as the docs beneath it
Custom internal web app	Build-your-own portal. Maximum control, but we'd become a software shop: development cost up front, maintenance forever, and search / permissions / editing that platforms include free.	$20k+ to build, plus upkeep	Skip Solves a problem we don't have

The Decision

The short version

Source One does not need another folder full of documents. It needs one operating system for how the company works — searchable, owned, current, and useful on a Monday morning.

Build it now. Start with CSR. Add AI after the knowledge is trusted.

Executive sponsorRemove roadblocks and make the system official.

Knowledge championOwn the library and spend 2–3 hours a week keeping it alive.

First proofA new or backup CSR handles a realistic order and exception using the documentation alone.

Protect the know-how

Critical work no longer walks out the door when someone retires, resigns, or takes a vacation.

Train people faster

New hires follow the same current playbook instead of inheriting whoever happens to train them.

Answer once

Managers link to an official answer instead of explaining the same process in email and chat forever.

Where We Are Exposed

The real risk

The problem is not that Source One has no documents. The problem is that the most important judgment still lives in a few people's heads.

Score each area on two questions: how badly does the company hurt if the expert disappears, and how much of that work is documented well enough for someone else to follow?

Illustrative positions. The risk score determines capture priority; the pilot also needs cross-functional reach and a fast, visible proof. That is why CSR can be the best pilot while payroll remains a priority risk.

Why CSR first

CSR sits at the intersection of clients, candidates, recruiting, sales, dispatch, and payroll handoffs. A successful CSR pilot demonstrates scripts, procedures, client-specific rules, system how-tos, and exception handling — and the benefit is visible every day.

What the Library Holds

Four shelves, not forty folders

Organize the library around the questions people actually ask: How do we do the work? What does this role own? What is different for this client? What rule applies here?

01 · Work

How the job gets done

Procedures, decision guides, scripts, templates, system walkthroughs, handoffs, and the edge cases veterans know by instinct.

02 · People

What each role owns

Job expectations, daily and weekly rhythms, onboarding paths, escalation routes, management routines, and offboarding.

03 · Clients

How each account really works

Contacts, site rules, commercial terms, history, worker fit, supervisor quirks, and the mistakes nobody wants to repeat.

04 · Rules

What changes by state or situation

Compliance, safety, payroll, HR, and state-specific requirements — labeled with jurisdiction, owner, and effective date.

Only six page shapes

SOPNumbered steps for one task
Decision guideIf A, do this; if B, do that
ChecklistHandoffs, onboarding, month-end
Role pageResponsibilities and daily rhythm
PolicyThe rule and the reason behind it
TemplateScripts, forms, emails, agreements

OwnerOne person accountable

VerifiedA visible review date

Applies toRole, client, and state

Edge casesThe “unless…” knowledge

Department Playbooks

What this looks like in real work

Every department uses the same system differently. The value comes from capturing the decisions, exceptions, and handoffs that matter to that team — then making the right answer retrievable at the moment of need.

Why CSR makes the best pilot: it touches nearly every other function, so one pilot proves that the library can improve daily work, cross-team handoffs, and exception handling at the same time.

CSR / Front Office Pilot

Faster answers, cleaner handoffs, more consistent client service

01 · Capture

Knowledge to capture

Order intake, fill, dispatch, confirmation, and daily opening/closing routines
Client check-in rules, contacts, scripts, and communication expectations
No-shows, walk-offs, injuries, complaints, unreachable candidates, and escalation paths

02 · Save

How it gets saved

Task-based SOPs with ATS or dispatch-board screenshots
Decision guides for the common exceptions
Client overlays linking account rules to the standard process
Approved phone and email templates

03 · Retrieve

What staff can retrieve

“What do I do when a worker no-shows?”
Who to contact and what to say for a specific client
The current fill-and-dispatch sequence
The correct handoff to recruiting, payroll, or management

04 · Use & benefit

Where it pays off

New and backup CSR training
Morning coverage and cross-branch continuity
Consistent client communication
Fewer dropped details when an order moves between teams

Sales

Protect margin, improve qualification, and hand off cleaner business

01 · Capture

Knowledge to capture

Ideal client profile, disqualifiers, and industries to prioritize
Discovery questions, decision-makers, and buying signals
Rate logic, markup guardrails, credit terms, and exception approvals
Proposal process and the sales-to-operations handoff

02 · Save

How it gets saved

Sales playbook and qualification decision tree
Approved proposal examples and reusable templates
Pricing and approval guide with permission controls
CRM field guide and handoff checklist

03 · Retrieve

What staff can retrieve

Whether an opportunity fits Source One
The approved pricing path and who can authorize an exception
The right discovery script and proposal language
Everything CSR, recruiting, payroll, and billing need at handoff

04 · Use & benefit

Where it pays off

Faster, more consistent proposals
Fewer bad-fit accounts and preventable margin leaks
Stronger coaching for new salespeople
Cleaner launches with less downstream rework

Recruiting / Candidates

Fill faster while keeping screening and onboarding consistent

01 · Capture

Knowledge to capture

Sourcing channels and tactics by job type
Screening questions, interview standards, and disqualifiers
Credentials, documents, background checks, and drug-screen rules
State-specific onboarding and redeployment practices

02 · Save

How it gets saved

Role-specific recruiting playbooks
Interview guides, scorecards, and candidate checklists
State-tagged document requirements
Reusable outreach, onboarding, and redeployment templates

03 · Retrieve

What staff can retrieve

Required documents for a worker in a specific state
The approved questions and screening criteria for a role
Credential or client-site requirements
Who is eligible and available for redeployment

04 · Use & benefit

Where it pays off

Quicker candidate screening and submittal
More consistent hiring decisions
Fewer missing documents at onboarding
Better retention and reuse of proven workers

Payroll

Create dependable backup coverage for a high-risk weekly process

01 · Capture

Knowledge to capture

The payroll calendar from timesheet receipt through deposit
Verification, entry, cutoff, approval, and reconciliation steps
Missing or disputed time, corrections, garnishments, and advances
Client and state-specific payroll rules

02 · Save

How it gets saved

Timed weekly SOP with system screenshots
Exception decision guides and approval paths
Client cutoff and timekeeping reference pages
Control checklist with owner and verification date

03 · Retrieve

What staff can retrieve

How to handle a missing or corrected timesheet
The cutoff and approval rule for a client
The right state leave or payroll requirement
Where a payroll exception must be escalated

04 · Use & benefit

Where it pays off

Reliable backup when the primary expert is unavailable
Fewer late or incorrect checks
Less rework and clearer controls
Faster training without risking a live payroll run

Accounting / Billing

Bill correctly, resolve disputes faster, and make collections consistent

01 · Capture

Knowledge to capture

Invoice cycles, formats, terms, portals, and client contacts
Collections cadence and escalation rules
Workers' compensation and unemployment claim handling
Month-end close and reconciliation routines

02 · Save

How it gets saved

Client billing profiles linked to account playbooks
Invoice and month-end checklists
Collections escalation matrix
Annotated examples of accepted invoice formats

03 · Retrieve

What staff can retrieve

How and when a client must be invoiced
The right billing contact, portal, and documentation
What action follows each aging stage
The next step in close or reconciliation

04 · Use & benefit

Where it pays off

Fewer rejected or disputed invoices
Faster billing and more disciplined collections
Smoother month-end coverage
Less dependence on one person's client memory

Management

Make decisions, escalations, and accountability consistent across branches

01 · Capture

Knowledge to capture

Decision rights, approval limits, and escalation paths
Branch and regional meeting rhythms, KPIs, and review standards
Internal hiring, coaching, discipline, and termination practices
Incident response and cross-functional ownership

02 · Save

How it gets saved

Role pages and responsibility map
Meeting agendas, KPI definitions, and review templates
Decision and escalation guides
Manager coaching and personnel-process playbooks

03 · Retrieve

What leaders can retrieve

Who owns or approves a decision
The definition and source of each KPI
The standard branch-review agenda
The correct response path for an incident or exception

04 · Use & benefit

Where it pays off

Faster escalation with fewer dropped issues
Consistent decisions across locations
Quicker onboarding for new managers
Clearer accountability and follow-through

Internal HR

Standardize the employee experience and close access gaps

01 · Capture

Knowledge to capture

Internal hiring, onboarding, equipment, accounts, and training
Benefits, PTO, handbook policies, and review cycles
Role changes, leaves, and employee-relations procedures
Offboarding, access removal, and knowledge transfer

02 · Save

How it gets saved

Employee lifecycle checklists
Controlled policy pages with effective dates
Role pages, manager guides, and standard forms
Access and equipment handoff templates

03 · Retrieve

What staff can retrieve

What a new internal hire needs on day one
The current policy or benefit process
How a review, role change, or leave is handled
Which systems and assets must be removed at departure

04 · Use & benefit

Where it pays off

Consistent onboarding across offices
Fewer missed forms, accounts, or equipment steps
More reliable policy answers
Cleaner offboarding and reduced access risk

Compliance & Safety

Turn changing rules into clear actions across every affected team

01 · Capture

Knowledge to capture

Federal, state, and local requirements with effective dates
Workplace injury, OSHA, and incident-reporting steps
E-Verify, ACA, certificates of insurance, and required postings
Client-site safety requirements and pending rule changes

02 · Save

How it gets saved

Jurisdiction-tagged summaries and change logs
Incident and reporting checklists
Rule pages linked to every SOP they modify
Client safety overlays with owner and review date

03 · Retrieve

What staff can retrieve

What changed, when it takes effect, and who owns the response
How to report and escalate an injury
Required forms, postings, or verification steps
The safety rules for a specific client site

04 · Use & benefit

Where it pays off

Faster, more consistent incident response
One change updates every affected department
Clearer audit and training evidence
Less risk from buried or outdated requirements

How We Capture It

Do not ask experts to write manuals

Veterans should talk and work. The champion does the writing. The owner verifies the result.

That division of labor protects expert time and captures what formal manuals miss: judgment, failure stories, client quirks, and the reason behind each step.

Watch the work

Interview the veteran while they perform the task. Record the screen. Ask where the process usually breaks and what they wish a new hire understood.

Turn it into a page

The champion converts the conversation into one of the six standard page shapes, with screenshots, labels, and clear decision points.

Verify and publish

The owner corrects the draft, signs it, sets the permission level, and makes it the official answer. Their job is fifteen minutes of review — not five hours of writing.

Offboarding becomes a capture event

Every departure triggers the same question: what does this person know that is still not written down? Use the notice period to capture clients, exceptions, routines, and pending work before access is removed.

How It Stays Trusted

A knowledge base is never finished

One stale answer can destroy confidence in the whole system. Every page needs an owner, a clock, and a visible path back to verification.

The standard: a new hire can see who verified the answer and when it was last checked.

Named ownership

One person signs each page. Anyone can suggest a change; one owner approves it.

Permissions first

Company, department, management, and payroll/HR access levels are set before sensitive content is loaded.

Change discipline

New law, client change, system change, incident, or documented mistake triggers an immediate review.

Visible updates

A short monthly “what changed” digest keeps the library in the flow of work.

Failed searchesWhat people need but cannot find

Stale pagesWhat has missed its review date

Repeat questionsWhat should become an article next

The Platform Decision

Buy the plumbing; own the knowledge

Start with a modern knowledge platform. Add an AI answer layer after the library is useful. Do not build a custom application for a problem established platforms already solve.

Start now

Modern wiki

Structured pages, search, templates, version history, and permission groups. Trial Notion and Guru with real CSR and front-office content; choose the one the champion can run without IT.

Planning range: $10–18 per user/month

Add later

AI answer layer

Employees ask in plain English and receive an answer linked to the source page. The AI does not replace the library; it makes a trusted library easier to use.

Planning range: $25–30 per user/month

Do not build

Custom app

More cost, slower launch, and permanent maintenance for search, editing, permissions, and version control that already exist off the shelf.

$20,000+ to build, plus upkeep

The sequence matters

Documents first. Adoption second. AI third. Putting AI in front of weak or stale content only produces wrong answers faster. Pricing above is a planning estimate; verify current vendor quotes before purchase.

The 90-Day Launch

Prove it before scaling it

The first 90 days should create one undeniable success, turn it into a repeatable method, and make the library part of normal work.

The rule: finish one stage well enough to reuse the method before adding more departments.

Name the champion

Give one respected, organized writer visible ownership and a standing weekly time commitment.

Score the risk

Leadership spends 30 minutes ranking the work. That ranking becomes the capture schedule.

Run the CSR pilot

Interview, record, draft, verify, and dry-run order intake, fill and dispatch, client communication, and common exceptions with a new or backup CSR.

Make the result official

Present the proof, fix the method, choose the next departments, and start linking to the library in daily work.

The approval needed now

Authorize a 30-day CSR pilot, name the champion, and approve a short platform trial using real work.