Keelridge

How it works

A disciplined operating layer—not a rip and replace.

Keelridge is being built around a recurring source-and-review process. The first supported path uses AMS Book exports and accounting reports; broader connectors come only after the narrow workflow is repeatable.

Walk through your source map
1
IMPLEMENTATION

Map the agency

Identify the recurring sources, fiscal definitions, GL classifications, role-to-Book assignments, benchmark tier, and assumptions behind the review.

  • Source and definition inventory
  • Initial data validation
  • Role and Book mapping
  • Owner review and training
2
RECURRING CLOSE

Stage and validate the files

The current pilot uses recurring manual files. Keelridge checks type, period, row shape, freshness, and anomalies before the data is accepted into reporting.

  • AMS Book snapshot
  • Accounting income and expense report
  • Visible period and freshness
  • Failure and exception review
3
OPERATING REVIEW

Review the agency by role

Owners and executives see agency financial and Book performance. Account managers see their own operational Book view. Each surface follows a specific job and data boundary.

  • Owner operating review
  • Manager team coverage
  • Account-manager My Book
  • Read-only analytic questions
4
SYSTEM HANDOFF

Return to the authoritative record

Keelridge can identify work and prepare context. Policy, client, service, billing, claim, and transaction activity remains in the AMS or accounting system that owns it.

  • No second policy master
  • No parallel E&O notes
  • No autonomous coverage decisions
  • No live AMS write-back today

Current pilot scope

Precise about what exists today.

The product will change. These boundaries keep the current story honest.

AreaCurrent behavior
Source intakeManual recurring AMS and accounting files, staged and validated before reporting
AMS supportInitial implementation focus: AMS 360-style Book export; not universal integration coverage
AccountingQuickBooks-style income and expense reports mapped into a governed chart
Product actionsAnalysis, review state, and human-owned workflow; no live AMS write-back
Analytic assistantRead-only, authorized metrics, numeric validation, and links to the owning view
Document knowledgeNot available in the live pilot until an approved corpus is indexed and role-tested
AvailabilityOne-agency pilot while security, onboarding, and repeatability are completed

Trust is a workflow

Evidence and people stay in control.

SOURCE

Know where the number came from

Operating and financial records retain their identity instead of becoming an unexplained blended total.

PERIOD

Know how current it is

Monthly reporting is only useful when the source period and freshness are visible.

ROLE

Project for responsibility

Owners and account teams receive different surfaces from the same governed inputs.

HUMAN

Keep judgment with the agency

Keelridge does not autonomously make licensed decisions or send unsupervised customer communication.

Start with the real process

Map the files and decisions behind your monthly review.

A useful first conversation can clarify the operating problem even if Keelridge is not yet the right fit.

Talk with the founder