FGH Software
ProductProcessEngagementsAbout
Skip to product content
Meet BASE

Your business, connected. Your next move, prepared.

BASE · Business Agentic Software Environment

BASE connects records across your business tools and prepares work for your team to review. Customer decisions stay with the people responsible for them.

See how it connectsExplore what BASE adds

One connected business

BASE relates the records in your tools so a follow-up can use the customer’s history and completed work can connect to billing.

One connected businessConceptual diagram

Each record holds part of the story.

BASEYour company contextRelated records within your dedicated environment
Select a record to explore how it contributes to the business story.

Follow the work

The same customer history stays available as an opportunity becomes delivery work and billing.

An opportunity connects to delivery and billing

  1. Find opportunities

    Research and review candidates.

  2. Win work

    Prepare and approve outreach.

  3. Keep it moving

    Track delivery and responsibility.

  4. Collect the money

    Inspect billing and payment state.

  5. Understand the business

    Inspect activity and supporting records.

Start with what needs you

See the work asking for attention and the preparation already done. Begin with the next decision instead of another round of checking applications.

Home and daily operations
Home workspace
Home workspaceScreenshot placeholder

Attention items, prepared drafts, completed activity, calendar context, and useful totals.

Screenshot placeholder · Home workspace

Prepared work. Human judgment.

Agents prepare the next step with business context. Your team reviews the work and controls consequential communications and decisions.

Outbox and approval
Draft approval
Draft approvalScreenshot placeholder

Prepared draft, supporting context, revisions, and the approval/send distinction.

Screenshot placeholder · Draft approval

Understand the whole system

Choose the part of the business you want to explore.

Shared foundation

A customer’s email can inform a follow-up; the job it leads to can connect to billing. BASE keeps those records related so your team can pick up the next step.

Connected workflows

Follow an inquiry through delivery, or look at a specific handoff that often gets missed. Each example shows where BASE prepares work and where a person decides.

Capabilities overview

Choose a workspace to see what happens behind the scenes and what your team reviews.

Feature directory

Browse the automation and connected workflows that go beyond ordinary manual work in each tool. Every row explains a specific feature.

Meet BASE

For the people keeping the business moving.

BASE helps when customer work crosses several tools and someone has to keep track of the handoffs. Each person sees the records and actions their role allows.

On this page

  • Who BASE helps

    Owner-led service businesses, teams coordinating work through email and spreadsheets, businesses with useful existing tools but poor connections between them, and companies with repeatable operational work that benefits from shared context.

    Existing vertical starting points include software, HVAC, insurance, and financial-advisor configurations. A pack is a configurable starting point, not a regulatory credential or proof of equal maturity in every sector.

  • Owner

    Start with attention items, the pipeline, financial findings, and recorded activity. Inspect supporting records and direct the next decision without assembling a picture across every tool.

  • Salesperson

    Research prospects, inspect relationship history, review prepared outreach, and keep follow-up connected to deal activity. Replies and stage changes provide evidence of what happened.

  • Office coordinator

    Review inbound messages, drafts, calendar context, and delivery handoffs. Help work reach the right person and keep the next action visible.

  • Financial reviewer

    Inspect invoices, synchronized payment status, supplier documents, job costs, and financial exceptions. Review uncertain records before accepting them.

  • Field visitor

    Plan stops with travel and visit time, record visit context, find nearby opportunities, and prepare follow-up after a day in the field.

The same environment, different responsibilities

People don’t all have the same access. Team units, assignments, document grants, and approval authority determine which records and actions each person can use.

Team access
Team accessScreenshot placeholder

Units, assignments, access scope, and approval responsibility.

Screenshot placeholder · Team access
Meet BASE

The work that falls between applications.

Recognizable gaps in ordinary business operations become the starting point for a connected workflow.

Follow-through depends on memory

A deal goes quiet when the next follow-up depends on someone remembering it. BASE prepares follow-through and records the activity so the team can see what happened.

Email intelligence

Find the messages that need attention and connect them to the customer’s history.

Sales pipeline and follow-through

Keep follow-up tied to the deal, with prepared messages and cadences that stop on replies.

The financial picture arrives in pieces

A job can be complete while its billing still waits in another application. Related records make the missing handoff easier to find, and supplier costs give the reviewer more context about margin.

Cross-system findings

A completed job with no linked invoice deserves a look. BASE flags record mismatches and brings the supporting information into the review.

Cross-system findingConceptual example

Completed job

Work is complete, with recorded value and customer context.

No linked invoice

The configured billing interval has passed without an invoice relationship.

Review item: completed work awaiting billing.

An opportunity to act, rather than a claim of recovered cash.

The next person starts from scratch

When someone picks up a customer’s work, they need the earlier conversations and the business rules behind it. BASE makes that history available within the person’s access permissions.

Company relationship records

Keep the relationship history available when another person picks up the work.

Documents and business knowledge

Give people and agents approved business documents they can use and review.

Meet BASE

Software businesses and BASE.

A configurable starting point built from the same connected capabilities.

An illustrative workflow

An inquiry leads to a researched opportunity, a reviewed proposal, delivery work, and billing follow-through.

This is a fictional workflow example, not a customer outcome or a regulatory credential.

An opportunity connects to delivery and billing

  1. Find opportunities

    Research and review candidates.

  2. Win work

    Prepare and approve outreach.

  3. Keep it moving

    Track delivery and responsibility.

  4. Collect the money

    Inspect billing and payment state.

  5. Understand the business

    Inspect activity and supporting records.

Configure around the business

Categories, approved knowledge, templates, agents, business hours, timezone, briefing preferences, follow-up cadences, branding, integrations, operating limits, outbound identity, trip defaults, and stated ROI rates can be configured around the business. Vertical packs provide starting points rather than replacing business-specific decisions.

Fit and responsibility

A vertical pack is a configurable starting point, not proof of equal maturity across sectors. Applicable professional, compliance, and customer decisions stay with the responsible people.

Who it helps

BASE helps when customer work crosses several tools and someone has to keep track of the handoffs. Each person sees the records and actions their role allows.

Configuration

Choose the categories and approved knowledge your team uses, then define responsibilities and workflow limits. Industry configurations provide a starting point.

Security and approval

Each client has a dedicated environment. Permissions limit the records people and agents can use, while approval history shows who authorized a communication.

Meet BASE

HVAC businesses and BASE.

A configurable starting point built from the same connected capabilities.

An illustrative workflow

A customer inquiry connects to scheduled work, job context, supplier costs, completion, and review-request preparation.

This is a fictional workflow example, not a customer outcome or a regulatory credential.

An opportunity connects to delivery and billing

  1. Find opportunities

    Research and review candidates.

  2. Win work

    Prepare and approve outreach.

  3. Keep it moving

    Track delivery and responsibility.

  4. Collect the money

    Inspect billing and payment state.

  5. Understand the business

    Inspect activity and supporting records.

Configure around the business

Categories, approved knowledge, templates, agents, business hours, timezone, briefing preferences, follow-up cadences, branding, integrations, operating limits, outbound identity, trip defaults, and stated ROI rates can be configured around the business. Vertical packs provide starting points rather than replacing business-specific decisions.

Fit and responsibility

A vertical pack is a configurable starting point, not proof of equal maturity across sectors. Applicable professional, compliance, and customer decisions stay with the responsible people.

Who it helps

BASE helps when customer work crosses several tools and someone has to keep track of the handoffs. Each person sees the records and actions their role allows.

Configuration

Choose the categories and approved knowledge your team uses, then define responsibilities and workflow limits. Industry configurations provide a starting point.

Security and approval

Each client has a dedicated environment. Permissions limit the records people and agents can use, while approval history shows who authorized a communication.

Meet BASE

Insurance businesses and BASE.

A configurable starting point built from the same connected capabilities.

An illustrative workflow

Prospect research and inbound conversations connect to relationship context, meeting preparation, approved knowledge, and reviewed follow-up.

This is a fictional workflow example, not a customer outcome or a regulatory credential.

An opportunity connects to delivery and billing

  1. Find opportunities

    Research and review candidates.

  2. Win work

    Prepare and approve outreach.

  3. Keep it moving

    Track delivery and responsibility.

  4. Collect the money

    Inspect billing and payment state.

  5. Understand the business

    Inspect activity and supporting records.

Configure around the business

Categories, approved knowledge, templates, agents, business hours, timezone, briefing preferences, follow-up cadences, branding, integrations, operating limits, outbound identity, trip defaults, and stated ROI rates can be configured around the business. Vertical packs provide starting points rather than replacing business-specific decisions.

Fit and responsibility

A vertical pack is a configurable starting point, not proof of equal maturity across sectors. Applicable professional, compliance, and customer decisions stay with the responsible people.

Who it helps

BASE helps when customer work crosses several tools and someone has to keep track of the handoffs. Each person sees the records and actions their role allows.

Configuration

Choose the categories and approved knowledge your team uses, then define responsibilities and workflow limits. Industry configurations provide a starting point.

Security and approval

Each client has a dedicated environment. Permissions limit the records people and agents can use, while approval history shows who authorized a communication.

Meet BASE

Financial-advisor businesses and BASE.

A configurable starting point built from the same connected capabilities.

An illustrative workflow

Prepare meetings from authorized relationship records and business knowledge, review documents against playbooks, and keep communication approval explicit.

This is a fictional workflow example, not a customer outcome or a regulatory credential.

An opportunity connects to delivery and billing

  1. Find opportunities

    Research and review candidates.

  2. Win work

    Prepare and approve outreach.

  3. Keep it moving

    Track delivery and responsibility.

  4. Collect the money

    Inspect billing and payment state.

  5. Understand the business

    Inspect activity and supporting records.

Configure around the business

Categories, approved knowledge, templates, agents, business hours, timezone, briefing preferences, follow-up cadences, branding, integrations, operating limits, outbound identity, trip defaults, and stated ROI rates can be configured around the business. Vertical packs provide starting points rather than replacing business-specific decisions.

Fit and responsibility

A vertical pack is a configurable starting point, not proof of equal maturity across sectors. Applicable professional, compliance, and customer decisions stay with the responsible people.

Who it helps

BASE helps when customer work crosses several tools and someone has to keep track of the handoffs. Each person sees the records and actions their role allows.

Configuration

Choose the categories and approved knowledge your team uses, then define responsibilities and workflow limits. Industry configurations provide a starting point.

Security and approval

Each client has a dedicated environment. Permissions limit the records people and agents can use, while approval history shows who authorized a communication.

One connected business

Keep the customer history with the work.

A customer’s email can inform a follow-up; the job it leads to can connect to billing. BASE keeps those records related so your team can pick up the next step.

On this page

Shared facts. Related work.

A customer’s email, deal, job, invoice, and payment status are related parts of the same business story.

One connected businessConceptual diagram

Each record holds part of the story.

BASEYour company contextRelated records within your dedicated environment
Select a record to explore how it contributes to the business story.

  • Context that carries forward

    An earlier conversation can inform a follow-up, while a payment update can change the next collection decision. Your team doesn’t have to rebuild the customer’s history every time the work changes hands.

    Related records

  • Mirror external tools; own the operational work

    • External mirrors: records brought in from an accounting system, calendar, project tool, file, or supported feed. The original tool can remain authoritative.
    • BASE-owned work: decisions, notes, drafts, approvals, instructions, agent feedback, and workflow history created in BASE.

    BASE records aren’t all read-only mirrors. Deals, drafts, approvals, and other native operational records have their own lifecycle.

  • Centralized does not mean everyone sees everything

    Access depends on the person, area, unit, assignment, document grants, and approval authority. The Assistant and agents operate through the same relevant access boundaries.

  • A dedicated environment for each client

    Each client has a dedicated application deployment and database. “Shared database” means shared context within that client's authorized environment, not a shared pool of every client's business content.

    The core system doesn’t include cross-client learning or pooled customer data. Company relationship records are part of the main system; deeper universal person/contact identity is a future expansion.

When the story does not line up

A finished job without a linked invoice is a gap worth investigating. BASE brings the related records together so someone can review it.

Cross-system findings

A completed job with no linked invoice deserves a look. BASE flags record mismatches and brings the supporting information into the review.

Cross-system findingConceptual example

Completed job

Work is complete, with recorded value and customer context.

No linked invoice

The configured billing interval has passed without an invoice relationship.

Review item: completed work awaiting billing.

An opportunity to act, rather than a claim of recovered cash.

One connected business

Records that keep their history.

See which records came from another tool and which your team created in BASE. Related records keep the history available as work changes hands.

The operational record families

BASE uses a central Postgres operational database for each client’s environment. Feature families work from related records instead of isolated application histories.

The database connects:

  • Companies and business relationships.
  • Inbound leads and researched prospects.
  • Deals, stages, notes, and sales events.
  • Emails, conversations, and follow-up flags.
  • Drafts, revisions, approvals, and send history.
  • Jobs, status changes, invoice links, and costs.
  • Customer invoices, balances, and payment status.
  • Suppliers, bills, purchase orders, and job cost lines.
  • Calendar events and meeting context.
  • Knowledge documents, instructions, templates, and versions.
  • Agent definitions, feedback, evaluations, and learning proposals.
  • Council sessions and review artifacts.
  • Locations, trips, stops, and field visits.
  • Import batches, mappings, and synchronization history.
  • Workflow runs, findings, and activity receipts.
  • Users, units, memberships, permissions, assignments, and business settings.
Data map and Sheets
Data map and SheetsScreenshot placeholder

Connected records, registered data, agents, applications, and readable tables.

Screenshot placeholder · Data map and Sheets

Relationships that carry forward

A company directory and company detail workspace gather related emails, prospects, deals, jobs, money, notes, and activity. A timeline helps the team understand what happened and when.

Preserve relationship context across people and workflows.

Company detail
Company detailScreenshot placeholder

Related emails, deals, jobs, money, notes, and the relationship timeline.

Screenshot placeholder · Company detail

Source identity and synchronization

External mirrors preserve the original tool’s identity and synchronization history. BASE-owned work records decisions, versions, approval, notes, and workflow outcomes. Connection health makes relevant freshness and failures available for review.

Data and portability

Check mappings and matches before an import lands. Saved source formats can handle repeat updates, while changed formats or unknown values wait for review.

Tools and connections

Some connections use a native adapter; others rely on files or supported feeds. Check the source coverage and setup requirements for each tool.

Teams and responsibility

Organize the business into units and assign responsibility for its records. Approval authority stays separate from permission to view or work on something.

Follow the work

See how the work moves through BASE.

Follow an inquiry through delivery, or look at a specific handoff that often gets missed. Each example shows where BASE prepares work and where a person decides.

  • An inquiry becomes work, then billing

    Inquiry → conversation → work → invoice → payment visibility.

    An inquiry arrives through a supported form or email path.

    Follow this workflow

  • Research a prospect before starting outreach

    Market search → assessment → pursuit → follow-up → reply.

    An operator defines a market.

    Follow this workflow

  • Find completed work that still needs an invoice

    Finished job → missing invoice → operator action.

    BASE compares completed work against invoice links after the configured grace period and surfaces the associated value.

    Follow this workflow

  • Review supplier costs against the job

    Supplier document → reviewed bill → job cost → margin context.

    BASE extracts supported information, validates it, stages it for review, and relates the accepted record to work.

    Follow this workflow

  • Keep field visits connected to follow-up

    Trip → visit → follow-up.

    Plan eligible destinations with travel and visit time, record what happened, and prepare follow-up from the visit context..

    Follow this workflow

  • Review a decision with a council of advisors

    Question → shared facts → council → reviewed response.

    An operator asks how to handle a discount request.

    Follow this workflow

  • Check an instruction change before it takes effect

    Correction → learning proposal → quality gate → versioned improvement.

    A user corrects an agent result.

    Follow this workflow
Follow the work

An inquiry becomes work, then billing.

An inquiry arrives through a supported form or email path.

How the work moves

An inquiry arrives through a supported form or email path. BASE records and surfaces it. A deal holds the sales context. The system prepares communications and reminders for review. Won work moves into Jobs. Completed work can be handed to invoicing. Accounting synchronization supplies payment status for financial follow-through.

People make the consequential decisions and review prepared communications; the stages aren’t all unattended actions.

An opportunity connects to delivery and billing

  1. Find opportunities

    Research and review candidates.

  2. Win work

    Prepare and approve outreach.

  3. Keep it moving

    Track delivery and responsibility.

  4. Collect the money

    Inspect billing and payment state.

  5. Understand the business

    Inspect activity and supporting records.

The workspace behind the workflow

The relevant workspace keeps the source context available while the team reviews the next step.

Sales opportunity
Sales opportunityScreenshot placeholder

Stages, notes, communication history, and the next action.

Screenshot placeholder · Sales opportunity

Explore the supporting capabilities

Look inside the parts of BASE that support this workflow.

Email intelligence

Find the messages that need attention and connect them to the customer’s history.

Sales pipeline and follow-through

Keep follow-up tied to the deal, with prepared messages and cadences that stop on replies.

Jobs and delivery follow-through

Track delivery and catch completed work that still needs billing follow-through.

Follow the work

Research a prospect before starting outreach.

An operator defines a market.

How the work moves

An operator defines a market. BASE finds candidates, researches evidence, prepares assessments, and presents a decision. Pursued prospects become sales work. Drafts await review and approved sends are recorded. A reply stops cadence progression.

Research becomes a reviewed opportunity

  1. Market search

    Define the business and geography.

  2. Assessment

    Inspect evidence and rationale.

  3. Pursuit

    A person decides to proceed.

  4. Follow-up

    Review prepared communications.

  5. Reply

    Stop cadence progression.

The workspace behind the workflow

The relevant workspace keeps the source context available while the team reviews the next step.

Lead assessment
Lead assessmentScreenshot placeholder

Fit score, rationale, website evidence, outreach angle, and the decision controls.

Screenshot placeholder · Lead assessment

Explore the supporting capabilities

Look inside the parts of BASE that support this workflow.

Lead discovery and intelligence

Research a defined market and review the evidence before choosing a prospect to pursue.

Sales pipeline and follow-through

Keep follow-up tied to the deal, with prepared messages and cadences that stop on replies.

Outbox and approval

Review a prepared message and its history before approving the send.

Follow the work

Find completed work that still needs an invoice.

BASE compares completed work against invoice links after the configured grace period and surfaces the associated value.

How the work moves

BASE compares completed work against invoice links after the configured grace period and surfaces the associated value. The finding becomes a concrete item to resolve.

Cross-system findingConceptual example

Completed job

Work is complete, with recorded value and customer context.

No linked invoice

The configured billing interval has passed without an invoice relationship.

Review item: completed work awaiting billing.

An opportunity to act, rather than a claim of recovered cash.

The workspace behind the workflow

The relevant workspace keeps the source context available while the team reviews the next step.

Uninvoiced-work finding
Uninvoiced-work findingScreenshot placeholder

Completed job, missing invoice relationship, associated value, and operator action.

Screenshot placeholder · Uninvoiced-work finding

Explore the supporting capabilities

Look inside the parts of BASE that support this workflow.

Jobs and delivery follow-through

Track delivery and catch completed work that still needs billing follow-through.

Cross-system findings

A completed job with no linked invoice deserves a look. BASE flags record mismatches and brings the supporting information into the review.

Receivables

Prepare collection follow-through using the accounting system’s balance and payment status.

Follow the work

Review supplier costs against the job.

BASE extracts supported information, validates it, stages it for review, and relates the accepted record to work.

How the work moves

BASE extracts supported information, validates it, stages it for review, and relates the accepted record to work. Costs contribute to margin context and financial checks.

Source to reviewed record

  1. Source

    Supported document intake.

  2. Extract

    Propose structured information.

  3. Check

    Ground fields and arithmetic.

  4. Review

    Confirm the staged result.

  5. Connect

    Relate accepted costs to work.

The workspace behind the workflow

The relevant workspace keeps the source context available while the team reviews the next step.

Document extraction
Document extractionScreenshot placeholder

Source preview, proposed structured fields, checks, and human confirmation.

Screenshot placeholder · Document extraction

Explore the supporting capabilities

Look inside the parts of BASE that support this workflow.

Document extraction

Turn a supplier document into proposed fields that someone can check before accepting.

Payables and margin

Connect supplier costs to jobs and investigate duplicate-charge or margin questions.

Cross-system findings

A completed job with no linked invoice deserves a look. BASE flags record mismatches and brings the supporting information into the review.

Follow the work

Keep field visits connected to follow-up.

Plan eligible destinations with travel and visit time, record what happened, and prepare follow-up from the visit context.

How the work moves

Plan eligible destinations with travel and visit time, record what happened, and prepare follow-up from the visit context.

Make field activity part of the story

  1. Plan

    Select destinations and time budget.

  2. Route

    Calculate travel and visit time.

  3. Visit

    Record the context and outcome.

  4. Follow up

    Prepare the next communication.

The workspace behind the workflow

The relevant workspace keeps the source context available while the team reviews the next step.

Geography trip
Geography tripScreenshot placeholder

Stops, route, travel/visit time budget, and visit follow-up.

Screenshot placeholder · Geography trip

Explore the supporting capabilities

Look inside the parts of BASE that support this workflow.

Geography and field sales

Plan field visits within a travel-time budget and keep the resulting follow-up connected.

Lead discovery and intelligence

Research a defined market and review the evidence before choosing a prospect to pursue.

Outbox and approval

Review a prepared message and its history before approving the send.

Follow the work

Review a decision with a council of advisors.

An operator asks how to handle a discount request.

How the work moves

An operator asks how to handle a discount request. The system assembles authorized facts. Relevant council seats independently review the options, discuss disagreements, and offer a recommendation. The operator chooses an approach and prepares a response in the normal draft workflow.

Shared facts, independent perspectives

  1. Common facts

    Freeze authorized context.

  2. Perspectives

    Independent initial opinions.

  3. Discussion

    Expose disagreement and missing facts.

  4. Recommendation

    Synthesize options and conditions.

  5. Your decision

    Return advice to the workflow.

The workspace behind the workflow

The relevant workspace keeps the source context available while the team reviews the next step.

Council review
Council reviewScreenshot placeholder

Common facts, independent perspectives, disagreements, and a recommendation.

Screenshot placeholder · Council review

Explore the supporting capabilities

Look inside the parts of BASE that support this workflow.

Council

Council asks selected advisors to consider the same authorized facts. You can compare their reasoning and disagreements before choosing an approach.

Custom advisors

Write the advisor’s instructions in plain language and connect approved documents. It can recommend an approach, but it doesn’t gain permission to send messages or change records.

Outbox and approval

Review a prepared message and its history before approving the send.

Follow the work

Check an instruction change before it takes effect.

A user corrects an agent result.

How the work moves

A user corrects an agent result. Eligible feedback supports a learning proposal. Evaluation and guardrails determine whether a change can be proposed or applied. The change has history and Undo; safety and approval rules remain enforced in code.

Supervised instruction improvement

  1. Correction

    Eligible feedback identifies a gap.

  2. Proposal

    Prepare an instruction change.

  3. Quality gate

    Evaluate and check regressions.

  4. Version

    Preserve origin and history.

  5. Inspect / Undo

    Keep the change reversible.

The workspace behind the workflow

The relevant workspace keeps the source context available while the team reviews the next step.

Agent manager
Agent managerScreenshot placeholder

Instructions, deliverables, supporting knowledge, feedback, evaluations, and health.

Screenshot placeholder · Agent manager

Explore the supporting capabilities

Look inside the parts of BASE that support this workflow.

Agent oversight

Define the agent’s instructions and the documents it can use, then check its work against the required deliverables. Feedback and evaluations help you judge proposed changes.

Learning

Corrections can lead to a proposed instruction change. Evaluations check eligible changes before approval or guarded automatic application, and version history lets you inspect or undo them.

Security and approval

Each client has a dedicated environment. Permissions limit the records people and agents can use, while approval history shows who authorized a communication.

Follow the work

A day with BASE.

An illustrative walkthrough of Cedar Service Company, a fictional business. The same people and records carry through the day.

On this page

Morning review

The coordinator at fictional Cedar Service Company opens the Home workspace to inspect attention items, drafts, activity, and upcoming calendar context.

A fictional business throughout the day

  1. Morning

    Review the work needing attention.

  2. Customer work

    Research and review communications.

  3. Preparation

    Connect meetings to context.

  4. Follow-through

    Inspect delivery and money.

  5. Review

    Check completed activity.

  • Prospecting

    The salesperson reviews a standing market watch, reads evidence and fit rationale, and decides which candidates to pursue.

  • Draft approval

    An authorized reviewer checks a prepared follow-up against the customer history, revises it, and uses the shared approval/send path.

  • Meeting preparation

    The Assistant gathers the relevant authorized company, deal, document, and calendar context for the next meeting.

  • Job follow-through

    The coordinator checks stale work, status changes, responsibility, and completed jobs ready for invoicing.

  • Financial exceptions

    The financial reviewer checks synchronized balances, partial payments, uninvoiced work, and supplier-cost findings before acting.

  • End-of-day review

    The owner reviews completed activity, unresolved findings, and the records behind them. Prepared work and completed actions stay distinct.

Fictional Cedar Service Company

Walk through the day.

Morning review

Review attention items, drafts, completed activity, and upcoming commitments.

Explore capabilities

What each part of BASE does.

Choose a workspace to see what happens behind the scenes and what your team reviews.

Find and win the work

Research prospects, understand incoming conversations, and prepare relevant follow-through.

Lead discovery and intelligence

Research a defined market and review the evidence before choosing a prospect to pursue.

Email intelligence

Find the messages that need attention and connect them to the customer’s history.

Sales pipeline and follow-through

Keep follow-up tied to the deal, with prepared messages and cadences that stop on replies.

Deliver and understand the money

Keep delivery connected to billing and review the financial exceptions that need attention.

Jobs and delivery follow-through

Track delivery and catch completed work that still needs billing follow-through.

Receivables

Prepare collection follow-through using the accounting system’s balance and payment status.

Payables and margin

Connect supplier costs to jobs and investigate duplicate-charge or margin questions.

Give the business shared context

Approved knowledge and supervised agents support the work around your team.

Documents and business knowledge

Give people and agents approved business documents they can use and review.

Agent oversight

Define the agent’s instructions and the documents it can use, then check its work against the required deliverables. Feedback and evaluations help you judge proposed changes.

Council

Council asks selected advisors to consider the same authorized facts. You can compare their reasoning and disagreements before choosing an approach.

Look inside each capability.

Choose a workspace to see the preparation, context, and controls behind it.

Home and daily operations

Start with pending decisions and prepared work instead of checking each application separately.

Email intelligence

Find the messages that need attention and connect them to the customer’s history.

Lead discovery and intelligence

Research a defined market and review the evidence before choosing a prospect to pursue.

Sales pipeline and follow-through

Keep follow-up tied to the deal, with prepared messages and cadences that stop on replies.

Outbox and approval

Review a prepared message and its history before approving the send.

Campaigns and templates

Compare outreach using recorded replies and later deal outcomes.

Company relationship records

Keep the relationship history available when another person picks up the work.

Jobs and delivery follow-through

Track delivery and catch completed work that still needs billing follow-through.

Receivables

Prepare collection follow-through using the accounting system’s balance and payment status.

Payables and margin

Connect supplier costs to jobs and investigate duplicate-charge or margin questions.

Documents and business knowledge

Give people and agents approved business documents they can use and review.

Document extraction

Turn a supplier document into proposed fields that someone can check before accepting.

Calendar

Prepare for upcoming meetings with the customer records alongside the calendar.

Geography and field sales

Plan field visits within a travel-time budget and keep the resulting follow-up connected.

SMS and missed-call recovery

Manage supported business texts with consent records and channel-specific controls.

Assistant

Ask about authorized records and turn the answer into work you can review.

Agents, quality, and learning

Set an agent’s responsibilities and review its output and instruction changes.

Custom agents and council reviews

Compare advice about the same business facts before making the decision yourself.

Reusable output formats

Reuse an approved report format instead of rebuilding the layout each time.

Data, imports, and connections

Review an import, save the source format, and check later synchronization results.

Teams and responsibility

Define who can work on records and who can approve consequential actions.

Reporting and receipts

Check completed activity and the evidence behind reported figures.

Explore capabilities

Home and daily operations

Start with pending decisions and prepared work instead of checking each application separately.

Home and daily operations in practice

A daily operations workspace combines attention items, prepared drafts, completed activity, pipeline summaries, calendar context, findings, and Quick Links. Operators can expand the workspace for focused review.

Home workspace
Home workspaceScreenshot placeholder

Attention items, prepared drafts, completed activity, calendar context, and useful totals.

Screenshot placeholder · Home workspace

  • Attention before navigation

    Attention items and prepared drafts bring pending decisions into the daily workspace. The operator can expand it for focused review. Calendar context sits alongside the pipeline and findings, connecting upcoming commitments to current work.

  • Preparation and completed activity

    Prepared work and recorded activity are distinguishable. The workspace helps the team see what still needs a person.

Part of a wider workflow

Related records, access, and review paths remain connected to the surrounding business context.

A day with BASE

An illustrative walkthrough of Cedar Service Company, a fictional business. The same people and records carry through the day.

Reporting and receipts

Review recorded sends and replies alongside workflow results. Financial findings and time estimates show their supporting records or assumptions, so you can judge what the figures mean.

Explore capabilities

Email intelligence

Find the messages that need attention and connect them to the customer’s history.

Email intelligence in practice

BASE organizes inbound email into business-specific categories, summarizes messages, identifies priority, extracts configured information, flags follow-up, groups conversations, and connects relevant messages to company records. Operators can correct classifications and turn prospective inbound messages into deals and lead assessments.

Email intelligence
Email intelligenceScreenshot placeholder

Business categories, priority, extracted information, and the related conversation.

Screenshot placeholder · Email intelligence

  • Understand an incoming message

    Business-specific categories, summaries, priority, and configured field extraction turn an incoming message into useful operational context.

  • Connect the conversation

    Conversation groups and company links preserve the history behind a message. Follow-up flags keep the next action visible.

  • Move a real inquiry forward

    An operator can correct a classification and turn prospective inbound messages into deals and lead assessments.

Part of a wider workflow

Related records, access, and review paths remain connected to the surrounding business context.

Connected workflows

Follow an inquiry through delivery, or look at a specific handoff that often gets missed. Each example shows where BASE prepares work and where a person decides.

Outbox and approval

Review a prepared message and its history before approving the send.

Explore capabilities

Lead discovery and intelligence

Research a defined market and review the evidence before choosing a prospect to pursue.

On this page

Lead discovery and intelligence in practice

Search by business type and geography, run standing market watches, find lookalikes, research websites, score fit, explain the reasoning, and review candidates before deciding to save, pursue, or dismiss them. Intelligence packs add website quality, existing-provider indicators, keywords, paid-tool signals, geographic relationships, and labeled pricing suggestions.

Lead assessment
Lead assessmentScreenshot placeholder

Fit score, rationale, website evidence, outreach angle, and the decision controls.

Screenshot placeholder · Lead assessment

  • Research a defined market

    Define the business type and geography to search. Lookalike discovery can supply additional candidates to review.

  • Keep a market watch running

    Standing market watches repeat discovery for a defined market, giving the salesperson candidates to assess without starting the search again.

  • Inspect the fit rationale

    Website evidence and intelligence signals support the assessment. Fit scores come with reasoning for the salesperson to review.

  • Choose which prospects to pursue

    Save, pursue, or dismiss a candidate after reviewing the evidence. Pursued prospects become connected sales work.

  • Part of a wider workflow

    Related records, access, and review paths remain connected to the surrounding business context.

    Connected workflowsSoftware businesses and BASE.
Explore capabilities

Sales pipeline and follow-through

Keep follow-up tied to the deal, with prepared messages and cadences that stop on replies.

Sales pipeline and follow-through in practice

Track deals, stages, notes, events, related communication, and outcomes. Prepare outreach using company context and approved templates. Use configurable follow-up cadences, pause when needed, halt progression on replies, and hand won work into the Jobs workflow.

Sales opportunity
Sales opportunityScreenshot placeholder

Stages, notes, communication history, and the next action.

Screenshot placeholder · Sales opportunity

  • Prepare outreach from the relationship

    Company context and approved templates inform a prepared message. Related communications, notes, and events remain with the deal.

  • Follow through without losing the conversation

    Configurable cadences prepare follow-up. Progression can pause and stops on replies, so the next step reflects the conversation.

  • Carry won work into delivery

    Deal stages and outcomes preserve sales history. Won work can move into Jobs with the surrounding business context.

Part of a wider workflow

Related records, access, and review paths remain connected to the surrounding business context.

Connected workflows

Follow an inquiry through delivery, or look at a specific handoff that often gets missed. Each example shows where BASE prepares work and where a person decides.

Jobs and delivery follow-through

Track delivery and catch completed work that still needs billing follow-through.

Explore capabilities

Outbox and approval

Review a prepared message and its history before approving the send.

On this page

Outbox and approval in practice

Review, edit, revise, regenerate, schedule, snooze, cancel, or send prepared communications. Inspect draft versions, context, provenance, approval, and send results. A full revision workspace supports long-form editing. Accepting a revision saves a version; sending is a separate operation.

Draft approval
Draft approvalScreenshot placeholder

Prepared draft, supporting context, revisions, and the approval/send distinction.

Screenshot placeholder · Draft approval

  • A draft with its supporting context

    Inspect the prepared message, its provenance, and its versions before deciding what the customer should receive.

  • Revise without sending

    Edit, regenerate, or use the full revision workspace. Accepting a revision saves a version; sending remains a separate operation.

  • Control when the message leaves

    Authorized people review and approve the communication. The approval and send results remain in its history.

  • Schedule it or hold it back

    Schedule or snooze a prepared message when the timing isn’t right. Cancel it when the communication is no longer needed.

  • Part of a wider workflow

    Related records, access, and review paths remain connected to the surrounding business context.

    Security and approvalCouncil
Explore capabilities

Campaigns and templates

Compare outreach using recorded replies and later deal outcomes.

Campaigns and templates in practice

Group deals into campaigns, associate templates, and inspect actual sends, replies, response timing, and later deal outcomes. Compare communication approaches using recorded activity. Keep counts visible and avoid unsupported conclusions from small samples.

Campaign scoreboard
Campaign scoreboardScreenshot placeholder

Actual sends, replies, response timing, templates, and later deal outcomes.

Screenshot placeholder · Campaign scoreboard

  • Connect templates to sales work

    Group deals into campaigns and associate the approved templates used for outreach.

  • Compare recorded responses

    Actual sends, replies, and response timing show what happened. Later deal outcomes add context beyond the first response. Visible counts support comparison. A small sample doesn’t establish that one approach will always perform better.

Part of a wider workflow

Related records, access, and review paths remain connected to the surrounding business context.

Reporting and receipts

Review recorded sends and replies alongside workflow results. Financial findings and time estimates show their supporting records or assumptions, so you can judge what the figures mean.

Money, time, and margin

Look at the preparation your team repeats and the follow-through it sometimes misses. Use your own activity and review-time assumptions to estimate the difference.

Explore capabilities

Company relationship records

Keep the relationship history available when another person picks up the work.

Company relationship records in practice

A company directory and company detail workspace gather related emails, prospects, deals, jobs, money, notes, and activity. A timeline helps the team understand what happened and when.

Company detail
Company detailScreenshot placeholder

Related emails, deals, jobs, money, notes, and the relationship timeline.

Screenshot placeholder · Company detail

  • One relationship, connected records

    Company detail gathers the conversations, opportunities, delivery work, and money related to the business.

  • Understand what happened and when

    The relationship timeline preserves notes and activity so a new team member can pick up the story.

  • Carry context across handoffs

    Sales and operations can work from the same relationship history, within their applicable access boundaries.

Part of a wider workflow

Related records, access, and review paths remain connected to the surrounding business context.

Shared foundation

A customer’s email can inform a follow-up; the job it leads to can connect to billing. BASE keeps those records related so your team can pick up the next step.

Related records

See which records came from another tool and which your team created in BASE. Related records keep the history available as work changes hands.

Explore capabilities

Jobs and delivery follow-through

Track delivery and catch completed work that still needs billing follow-through.

Jobs and delivery follow-through in practice

Manage native or imported work records, status, customer relationships, values, costs, reminders, quote nudges, review requests, maintenance resurfacing, and invoice handoff. Surface stale work and completed jobs awaiting billing.

Job detail
Job detailScreenshot placeholder

Status, responsibility, values, costs, and invoice relationship.

Screenshot placeholder · Job detail

  • Keep delivery connected

    Native or imported work records carry customer relationships, responsibility, status, values, and costs.

  • Prepare lifecycle follow-through

    Configured reminders, quote nudges, review requests, and maintenance resurfacing support the work around delivery.

  • Connect completion to billing

    Stale-work checks and completed-job findings surface work that needs attention. Invoice handoff connects delivery to financial follow-through.

Part of a wider workflow

Related records, access, and review paths remain connected to the surrounding business context.

Cross-system findings

A completed job with no linked invoice deserves a look. BASE flags record mismatches and brings the supporting information into the review.

Receivables

Prepare collection follow-through using the accounting system’s balance and payment status.

Explore capabilities

Receivables

Prepare collection follow-through using the accounting system’s balance and payment status.

Receivables in practice

Inspect invoices, balances, overdue items, reminder preparation, payment-state synchronization, partial-payment exceptions, and stale data. QuickBooks read-back observes the accounting source; safe onboarding includes a shadow mode before going live.

Payment-aware follow-through
Payment-aware follow-throughScreenshot placeholder

Invoice balances, synchronized payment states, and reviewable reminders.

Screenshot placeholder · Payment-aware follow-through

  • Read the accounting state

    The read-only QuickBooks adapter supplies invoice balances and payment state. Connection freshness remains relevant to the view.

  • Prepare appropriate follow-through

    Reminder preparation uses the available balance context. Partial-payment exceptions and stale data need review before acting.

  • Review before going live

    Shadow-mode onboarding lets the team inspect the accounting connection and proposed follow-through before activation.

Part of a wider workflow

Related records, access, and review paths remain connected to the surrounding business context.

Tools and connections

Some connections use a native adapter; others rely on files or supported feeds. Check the source coverage and setup requirements for each tool.

Cross-system findings

A completed job with no linked invoice deserves a look. BASE flags record mismatches and brings the supporting information into the review.

Explore capabilities

Payables and margin

Connect supplier costs to jobs and investigate duplicate-charge or margin questions.

Payables and margin in practice

Connect supplier bills and purchase orders to work, tag costs to jobs, inspect margins, and surface possible duplicate charges, missing purchase orders, and margin erosion.

Payables finding
Payables findingScreenshot placeholder

Supplier bill, job costs, flagged issue, and the supporting evidence.

Screenshot placeholder · Payables finding

  • Relate supplier costs to the work

    Bills and purchase orders connect to jobs. Cost tagging supplies the context for reviewing delivery margin.

  • Surface questions worth checking

    Possible duplicate charges and missing purchase orders become findings to investigate against the supporting records.

  • Inspect margin erosion

    Job values and costs make the relationship visible. A flagged cost issue is an investigation, not confirmed recovered money.

Part of a wider workflow

Related records, access, and review paths remain connected to the surrounding business context.

Cross-system findings

A completed job with no linked invoice deserves a look. BASE flags record mismatches and brings the supporting information into the review.

Money, time, and margin

Look at the preparation your team repeats and the follow-through it sometimes misses. Use your own activity and review-time assumptions to estimate the difference.

Explore capabilities

Documents and business knowledge

Give people and agents approved business documents they can use and review.

On this page

Documents and business knowledge in practice

Store and version company knowledge, policies, pricing, procedures, agent instructions, review playbooks, templates, and brand guidance. Browse connected Drive files and synchronize selected files into knowledge. Review documents against playbooks and retain reports and history.

Business knowledge
Business knowledgeScreenshot placeholder

Approved documents, versions, agent bindings, and access grants.

Screenshot placeholder · Business knowledge

  • Give agents approved business knowledge

    Policies, pricing guidance, procedures, instructions, and templates provide the business context behind an answer.

  • Keep changes and access visible

    Knowledge is versioned. Selected connected Drive files can be synchronized, and document grants define who can use the material.

  • Review against a playbook

    Approved review criteria support repeatable document checks. Written reports and history preserve the review result.

  • Part of a wider workflow

    Related records, access, and review paths remain connected to the surrounding business context.

    Custom advisorsReusable output formats

Document review against a playbook

Review a document against approved criteria, inspect the written report, and retain the review history.

Document review
Document reviewScreenshot placeholder

Selected playbook, review result, written report, and history.

Screenshot placeholder · Document review
Explore capabilities

Document extraction

Turn a supplier document into proposed fields that someone can check before accepting.

Document extraction in practice

Read supported PDFs, scans, photos, receipts, and supplier documents. Propose structured fields, run grounding and arithmetic checks, and stage the result for human review. Intake can originate from uploads, configured supplier attachments, and watched Drive folders.

Document extraction
Document extractionScreenshot placeholder

Source preview, proposed structured fields, checks, and human confirmation.

Screenshot placeholder · Document extraction

  • Bring the source into review

    Supported uploads, configured supplier attachments, and watched Drive folders can supply PDFs, scans, photos, or receipts.

  • Propose fields and check the result

    Extraction proposes structured values. Grounding and arithmetic checks help identify results that require attention.

  • Confirm before accepting the record

    The source and proposed fields stay reviewable. A person checks uncertain financial information before the accepted record enters the work.

Part of a wider workflow

Related records, access, and review paths remain connected to the surrounding business context.

Data and portability

Check mappings and matches before an import lands. Saved source formats can handle repeat updates, while changed formats or unknown values wait for review.

Connected workflows

Follow an inquiry through delivery, or look at a specific handoff that often gets missed. Each example shows where BASE prepares work and where a person decides.

Explore capabilities

Calendar

Prepare for upcoming meetings with the customer records alongside the calendar.

Calendar in practice

Mirror multiple calendars, review Month, Week, and Week agenda views, inspect events and selected-day context, prepare for meetings, and confirm supported event creation and invitations.

Calendar and meeting context
Calendar and meeting contextScreenshot placeholder

Month, Week, agenda, and selected-day business context.

Screenshot placeholder · Calendar and meeting context

  • Bring calendars into the business view

    Multiple calendar mirrors provide upcoming commitments in Month, Week, and agenda views. Selected-day context and authorized relationship records help the team prepare for meetings.

  • Confirm supported scheduling actions

    Supported event creation and invitations use a confirmation path. A mirror and a confirmed action have different roles.

Part of a wider workflow

Related records, access, and review paths remain connected to the surrounding business context.

Assistant

The Assistant answers questions using the records you can access. It can also prepare a meeting brief or draft a message; supported actions still need the applicable confirmation.

A day with BASE

An illustrative walkthrough of Cedar Service Company, a fictional business. The same people and records carry through the day.

Explore capabilities

Geography and field sales

Plan field visits within a travel-time budget and keep the resulting follow-up connected.

On this page

Geography and field sales in practice

Review business destinations, check location pins, plan trips, calculate ordered stops, budget travel and visit time, record visits, prepare follow-up, and find nearby opportunities.

Geography trip
Geography tripScreenshot placeholder

Stops, route, travel/visit time budget, and visit follow-up.

Screenshot placeholder · Geography trip

  • Plan a workable day in the field

    Review business destinations, check pins, and calculate ordered stops with a travel and visit-time budget.

  • Keep the visit in the relationship

    Record what happened at a stop so the resulting context remains available after the trip.

  • Prepare the next conversation

    Visit context informs the follow-up, so the salesperson can prepare the next conversation around what happened on the trip.

  • Find prospects near the route

    Nearby opportunities can become additional destinations to review when planning field work.

  • Part of a wider workflow

    Related records, access, and review paths remain connected to the surrounding business context.

    Connected workflowsLead discovery and intelligence
Explore capabilities

SMS and missed-call recovery

Manage supported business texts with consent records and channel-specific controls.

SMS and missed-call recovery in practice

Manage two-way business texting, consent and opt-out records, lifecycle reminders, review requests, and missed-call textback through supported workflows. Channel activation is part of onboarding and includes provider registration and configuration.

SMS workflow
SMS workflowScreenshot placeholder

Conversation, consent-aware controls, and missed-call context.

Screenshot placeholder · SMS workflow

  • Keep two-way messages connected

    Supported business texting brings the conversation into the operational workflow with consent and opt-out records.

  • Prepare channel-specific follow-through

    Lifecycle reminders, review requests, and missed-call textback use the supported channel workflows and their controls.

  • Activate the channel deliberately

    Provider registration, account configuration, consent controls, and channel gates are part of onboarding.

Part of a wider workflow

Related records, access, and review paths remain connected to the surrounding business context.

Tools and connections

Some connections use a native adapter; others rely on files or supported feeds. Check the source coverage and setup requirements for each tool.

Security and approval

Each client has a dedicated environment. Permissions limit the records people and agents can use, while approval history shows who authorized a communication.

Explore capabilities

Assistant

Ask about authorized records and turn the answer into work you can review.

Assistant in practice

Ask business questions, search authorized records, inspect financial and operational context, prepare meetings, review documents, research the web, draft communications, and initiate supported confirmed actions. The Assistant supports conversation history, account-specific memory, file context, analysis, and visible progress.

Assistant conversation
Assistant conversationScreenshot placeholder

A business question, record-linked answer, and supported next step.

Screenshot placeholder · Assistant conversation

  • Ask from authorized business context

    Questions can use the records and documents the account is permitted to access, with supporting context available for inspection.

  • Prepare useful work in the conversation

    Meeting preparation, document review, research, and drafting turn the available context into a reviewable next step.

  • Confirm supported actions

    The Assistant can initiate supported confirmed actions. Conversation context doesn’t bypass the permissions checked when actions execute.

Part of a wider workflow

Related records, access, and review paths remain connected to the surrounding business context.

Assistant

The Assistant answers questions using the records you can access. It can also prepare a meeting brief or draft a message; supported actions still need the applicable confirmation.

Council

Council asks selected advisors to consider the same authorized facts. You can compare their reasoning and disagreements before choosing an approach.

Explore capabilities

Agents, quality, and learning

Set an agent’s responsibilities and review its output and instruction changes.

Agents, quality, and learning in practice

Manage a directory of agents, their instructions, bound documents, required deliverables, feedback, health, evaluations, and learning changes. Versioned instructions, proposal review, guarded automatic improvements, regression checks, and Undo make changes available for review. Authorized administrators manage technical model configuration.

Agent manager
Agent managerScreenshot placeholder

Instructions, deliverables, supporting knowledge, feedback, evaluations, and health.

Screenshot placeholder · Agent manager

  • Define what an agent is responsible for

    Instructions, bound documents, and required deliverables give each agent a supervised role.

  • Inspect quality and health

    Feedback, evaluations, health, and regression checks help administrators inspect behavior and proposed improvements.

  • Review instruction changes

    Versioned proposals, guarded automatic improvements, and Undo make eligible learning changes available for review.

Part of a wider workflow

Related records, access, and review paths remain connected to the surrounding business context.

Agent oversight

Define the agent’s instructions and the documents it can use, then check its work against the required deliverables. Feedback and evaluations help you judge proposed changes.

Learning

Corrections can lead to a proposed instruction change. Evaluations check eligible changes before approval or guarded automatic application, and version history lets you inspect or undo them.

Explore capabilities

Custom agents and council reviews

Compare advice about the same business facts before making the decision yourself.

Custom agents and council reviews in practice

Define specialized read-only advisory agents in plain-language documents. Use them on records or through the Assistant. Assemble a council of relevant perspectives to review a question, compare options, expose disagreements, and propose a recommendation. Return the advice to the original workflow as a suggestion.

Council review
Council reviewScreenshot placeholder

Common facts, independent perspectives, disagreements, and a recommendation.

Screenshot placeholder · Council review

  • Give specialists the relevant facts

    Plain-language documents define read-only advisors. Authorized records and bound knowledge support their perspective.

  • Compare perspectives on a shared question

    Council seats consider common facts, expose disagreements, and synthesize options into a recommendation.

  • Bring the advice back to the operator

    Advice returns to the original workflow as a suggestion. The person retains decision and approval authority.

Part of a wider workflow

Related records, access, and review paths remain connected to the surrounding business context.

Custom advisors

Write the advisor’s instructions in plain language and connect approved documents. It can recommend an approach, but it doesn’t gain permission to send messages or change records.

Council

Council asks selected advisors to consider the same authorized facts. You can compare their reasoning and disagreements before choosing an approach.

Explore capabilities

Reusable output formats

Reuse an approved report format instead of rebuilding the layout each time.

Reusable output formats in practice

Use versioned output templates and brand guidance for reports, documents, one-pagers, and other structured artifacts. Agents fill defined content slots; controlled rendering determines layout and validated arithmetic determines computed values. Review extracted template outlines before adopting them.

Branded output
Branded outputScreenshot placeholder

Structured report or one-pager, approved branding, and validated computed fields.

Screenshot placeholder · Branded output

  • Define the recurring format

    Versioned output templates and brand guidance establish the structure for reports, documents, and one-pagers. Extracted template outlines remain reviewable before becoming the format used for recurring outputs.

  • Fill the content without reinventing the layout

    Agents fill defined content slots. Controlled rendering determines the presentation and validated arithmetic supplies computed values.

Part of a wider workflow

Related records, access, and review paths remain connected to the surrounding business context.

Documents and business knowledge

Give people and agents approved business documents they can use and review.

Data and portability

Check mappings and matches before an import lands. Saved source formats can handle repeat updates, while changed formats or unknown values wait for review.

Explore capabilities

Data, imports, and connections

Review an import, save the source format, and check later synchronization results.

Data, imports, and connections in practice

Inspect authorized data through Sheets, Map, Grid, and Table views. Import supported files or pasted data, confirm mappings and matches, review changes, and land approved records in one transaction. Save source-specific formats and manage scheduled export pulls. View connection health, setup requirements, and synchronization results. Add company notes and business-specific custom fields through the data experience.

Data map and Sheets
Data map and SheetsScreenshot placeholder

Connected records, registered data, agents, applications, and readable tables.

Screenshot placeholder · Data map and Sheets

  • Inspect the available business data

    Authorized Sheets, Map, Grid, and Table views make related records readable. Company notes and custom fields provide business-specific context.

  • Review an import before it lands

    Confirm mappings and matches, inspect changes, and approve the staged records before they land in one transaction.

  • Reuse a known source format

    Saved source-specific mappings support scheduled export pulls. Connection health and synchronization results show how the data arrived.

Part of a wider workflow

Related records, access, and review paths remain connected to the surrounding business context.

Data and portability

Check mappings and matches before an import lands. Saved source formats can handle repeat updates, while changed formats or unknown values wait for review.

Tools and connections

Some connections use a native adapter; others rely on files or supported feeds. Check the source coverage and setup requirements for each tool.

Explore capabilities

Teams and responsibility

Define who can work on records and who can approve consequential actions.

Teams and responsibility in practice

Organize the business into company, region, location, team, or crew units. Manage memberships, assignments, shared pools, area-specific authority, approval routing, and organizational changes with previews and audit records.

Team access
Team accessScreenshot placeholder

Units, assignments, access scope, and approval responsibility.

Screenshot placeholder · Team access

  • Organize around real responsibility

    Nested company, region, location, team, or crew units connect memberships and assignments to the business structure.

  • Separate access from authority

    Area-specific grants define who can view, work, approve, or administer. Shared pools and assignments determine the available work.

  • Review organizational changes

    Move or deactivate people with previews, reassigned responsibilities, and audit records. Historical actor attribution remains with the work.

Part of a wider workflow

Related records, access, and review paths remain connected to the surrounding business context.

Teams and responsibility

Organize the business into units and assign responsibility for its records. Approval authority stays separate from permission to view or work on something.

Security and approval

Each client has a dedicated environment. Permissions limit the records people and agents can use, while approval history shows who authorized a communication.

Explore capabilities

Reporting and receipts

Check completed activity and the evidence behind reported figures.

Reporting and receipts in practice

Review sales and operational metrics, real activity counts, financial findings, stated-assumption time estimates, period statements, weekly narratives, workflow runs, connection health, and usage receipts.

Value statement
Value statementScreenshot placeholder

Activity counts, stated assumptions, financial findings, and the reporting period.

Screenshot placeholder · Value statement

  • Inspect recorded activity

    Actual sends, replies, workflow runs, and connection results provide evidence of the work performed.

  • Relate figures to supporting records

    Financial findings, period statements, and weekly narratives connect reported figures to their business context.

  • Keep estimates transparent

    Time estimates expose preparation and review assumptions. Usage receipts measure activity separately from business results.

Part of a wider workflow

Related records, access, and review paths remain connected to the surrounding business context.

Reporting and receipts

Review recorded sends and replies alongside workflow results. Financial findings and time estimates show their supporting records or assumptions, so you can judge what the figures mean.

Money, time, and margin

Look at the preparation your team repeats and the follow-through it sometimes misses. Use your own activity and review-time assumptions to estimate the difference.

People and agents

Ask about your actual business records.

The Assistant answers questions using the records you can access. It can also prepare a meeting brief or draft a message; supported actions still need the applicable confirmation.

The Assistant

Ask business questions, search authorized records, inspect financial and operational context, prepare meetings, review documents, research the web, draft communications, and initiate supported confirmed actions. The Assistant supports conversation history, account-specific memory, file context, analysis, and visible progress.

Reduce the effort of finding information and translating it into a next step.

Assistant conversation
Assistant conversationScreenshot placeholder

A business question, record-linked answer, and supported next step.

Screenshot placeholder · Assistant conversation

Questions grounded in your work

Examples: “What needs attention?” “Which completed jobs have no linked invoice?” “Prepare me for the customer meeting.” “What do we know about this company?” Answers can link to supporting records rather than relying on a conversation alone.

Multi-step assistance

The Assistant can plan bounded sequences of tool use, advisory review, and user questions. Steps have recorded results and required deliverables. Existing confirmation governs writes, and completion is checked against the ask.

Your context and access

Conversation history, account-specific memory, attached files, bounded analysis, and visible progress support the work. Account permissions are checked when supported actions execute.

Teams and responsibility

Organize the business into units and assign responsibility for its records. Approval authority stays separate from permission to view or work on something.

Security and approval

Each client has a dedicated environment. Permissions limit the records people and agents can use, while approval history shows who authorized a communication.

Custom advisors

Write the advisor’s instructions in plain language and connect approved documents. It can recommend an approach, but it doesn’t gain permission to send messages or change records.

Council

Council asks selected advisors to consider the same authorized facts. You can compare their reasoning and disagreements before choosing an approach.

People and agents

Give each agent a job you can review.

Define the agent’s instructions and the documents it can use, then check its work against the required deliverables. Feedback and evaluations help you judge proposed changes.

Agent directory

Users see the agents appropriate to their access, their role, instructions, required deliverables, supporting documents, and health. Administrators can manage technical configuration through authorized controls.

Agent manager
Agent managerScreenshot placeholder

Instructions, deliverables, supporting knowledge, feedback, evaluations, and health.

Screenshot placeholder · Agent manager

Quality checks

Required deliverables, structured checks, evaluations, held-out examples, regression safeguards, and independent verification help supervise work where configured. They reduce failure modes without guaranteeing perfect answers.

Feedback and improvement

Corrections and explicit feedback can support versioned improvements. Show Off, Propose, and guarded Auto learning as understandable choices. Improvements remain testable, available for review, and reversible.

Supervised instruction improvement

  1. Correction

    Eligible feedback identifies a gap.

  2. Proposal

    Prepare an instruction change.

  3. Quality gate

    Evaluate and check regressions.

  4. Version

    Preserve origin and history.

  5. Inspect / Undo

    Keep the change reversible.

Supporting context

Manage a directory of agents, their instructions, bound documents, required deliverables, feedback, health, evaluations, and learning changes. Versioned instructions, proposal review, guarded automatic improvements, regression checks, and Undo make changes available for review. Authorized administrators manage technical model configuration.

Make agent behavior a supervised business capability that improves with useful feedback.

Learning

Corrections can lead to a proposed instruction change. Evaluations check eligible changes before approval or guarded automatic application, and version history lets you inspect or undo them.

Custom advisors

Write the advisor’s instructions in plain language and connect approved documents. It can recommend an approach, but it doesn’t gain permission to send messages or change records.

Documents and business knowledge

Give people and agents approved business documents they can use and review.

People and agents

Create an advisor for a specific question.

Write the advisor’s instructions in plain language and connect approved documents. It can recommend an approach, but it doesn’t gain permission to send messages or change records.

Custom agents

A plain-language instruction document defines a specialized advisory agent. Bound business knowledge and permission-scoped context support its answer. Illustrative examples include a quote reviewer, late-payer advisor, or a company-specific decision reviewer; these examples aren’t a promise of preconfigured offerings.

Custom advisory agent
Custom advisory agentScreenshot placeholder

Plain-language instructions, approved knowledge, and labeled advisory output.

Screenshot placeholder · Custom advisory agent

Examples of advisory roles

Illustrative examples include a quote reviewer, late-payer advisor, or company-specific decision reviewer. Their output is advice for the person responsible for the decision.

Permission-scoped advice

Bound documents and authorized records support the response. An advisor doesn’t gain permission to send messages or change records simply because it recommends an action.

Council

Council asks selected advisors to consider the same authorized facts. You can compare their reasoning and disagreements before choosing an approach.

Security and approval

Each client has a dedicated environment. Permissions limit the records people and agents can use, while approval history shows who authorized a communication.

Teams and responsibility

Organize the business into units and assign responsibility for its records. Approval authority stays separate from permission to view or work on something.

People and agents

Get a second opinion with the facts attached.

Council asks selected advisors to consider the same authorized facts. You can compare their reasoning and disagreements before choosing an approach.

How a council review works

A user brings a question or item for review. Selected seats consider the same frozen authorized facts from their respective perspectives. Independent opinions, bounded rebuttal, and synthesis expose agreements, disagreements, and the facts that would settle them. The operator chooses what to do.

Possible perspectives include Sales, Finance, Jobs, Leads, Payables, Opportunity, Skeptic, Numbers, and Recipient. A compliance perspective flags issues for professional review; it doesn’t provide certification or replace counsel.

Shared facts, independent perspectives

  1. Common facts

    Freeze authorized context.

  2. Perspectives

    Independent initial opinions.

  3. Discussion

    Expose disagreement and missing facts.

  4. Recommendation

    Synthesize options and conditions.

  5. Your decision

    Return advice to the workflow.

Council review
Council reviewScreenshot placeholder

Common facts, independent perspectives, disagreements, and a recommendation.

Screenshot placeholder · Council review

Return to work

Council advice can return to a draft, review, deal note, or Assistant conversation as a suggestion. Applying advice follows the existing workflow and creates traceable versions where applicable. The council itself doesn’t send, edit records, or count as realized savings.

Review depth and history

Quick and Full reviews support bounded discussions. Review seat reports, options, conditions, agreements, disagreements, and session history. Source changes can require a fresh review.

Custom advisors

Write the advisor’s instructions in plain language and connect approved documents. It can recommend an approach, but it doesn’t gain permission to send messages or change records.

Outbox and approval

Review a prepared message and its history before approving the send.

Assistant

The Assistant answers questions using the records you can access. It can also prepare a meeting brief or draft a message; supported actions still need the applicable confirmation.

People and agents

Review how an agent’s instructions change.

Corrections can lead to a proposed instruction change. Evaluations check eligible changes before approval or guarded automatic application, and version history lets you inspect or undo them.

Feedback into improvement

Corrections and explicit feedback can support versioned improvements. Show Off, Propose, and guarded Auto learning as understandable choices. Improvements remain testable, available for review, and reversible.

Supervised instruction improvement

  1. Correction

    Eligible feedback identifies a gap.

  2. Proposal

    Prepare an instruction change.

  3. Quality gate

    Evaluate and check regressions.

  4. Version

    Preserve origin and history.

  5. Inspect / Undo

    Keep the change reversible.

Off, Propose, or guarded Auto

Turn learning off, review proposals, or use guarded automatic instruction improvement where supported. Required deliverables, curated evaluation cases, held-out examples, and regression checks help supervise changes.

Safe learning

Versioned instruction changes, evaluation gates, regression safeguards, and Undo help supervise improvements. Learning changes agent instructions, not the immutable safety rules.

Inspect and reverse

Instruction history preserves change origin and version. Inspect eligible proposals, accept or reject them, and Undo supported automatic changes.

Agent manager
Agent managerScreenshot placeholder

Instructions, deliverables, supporting knowledge, feedback, evaluations, and health.

Screenshot placeholder · Agent manager
See the value

See where BASE could save your team work.

Look at the preparation your team repeats and the follow-through it sometimes misses. Use your own activity and review-time assumptions to estimate the difference.

Work more of the right opportunities

Repeatable research and prepared follow-through help the team pursue relevant work with the relationship context already available.

Lead discovery and intelligence

Research a defined market and review the evidence before choosing a prospect to pursue.

Sales pipeline and follow-through

Keep follow-up tied to the deal, with prepared messages and cadences that stop on replies.

Notice the financial gaps

Completed work without an invoice and costs without clear job context are questions worth checking. Findings link to the records behind them.

Cross-system findings

A completed job with no linked invoice deserves a look. BASE flags record mismatches and brings the supporting information into the review.

Cross-system findingConceptual example

Completed job

Work is complete, with recorded value and customer context.

No linked invoice

The configured billing interval has passed without an invoice relationship.

Review item: completed work awaiting billing.

An opportunity to act, rather than a claim of recovered cash.

Spend less effort preparing

Drafting and context gathering become reviewable starting points. The value depends on your actual preparation and review effort.

The work behind a value estimate.

Check how an activity could affect revenue or reduce preparation time. Pipeline value, issued invoices, and collected payments measure different things.

Estimate from your own assumptions

Use your own preparation time, review time, and monthly volume. The result is an illustration, not a savings guarantee.

Illustrative calculation

Use your own time assumptions.

Estimate preparation effort reduced after accounting for human review. These starting values are illustrative, not observed customer results.

1.7 hours per month5 minutes per message × 20 messages ÷ 60. Review is retained in the calculation.

An estimated reduction in preparation effort is not a completed customer communication or a guaranteed saving. If review takes longer than preparation, this estimate shows zero reduction.

Workflow assessment

Where does work fall between tools?

Select the situations you recognize. This is a conversation starter rather than a diagnostic score or financial forecast.

Choose a situation to identify a workflow worth discussing.

See the value

The work behind a value estimate.

Check how an activity could affect revenue or reduce preparation time. Pipeline value, issued invoices, and collected payments measure different things.

How BASE helps make money

OpportunityMechanismEvidence to show
Find more relevant prospectsRepeatable discovery and researchReviewed and pursued prospects
Work more existing opportunitiesFollow-up preparation and cadence trackingSends, replies, and stage changes
Reduce overlooked inquiriesIntake, triage, and attention itemsInquiry and follow-up history
Recover overlooked billingCompleted-but-uninvoiced findingsJob values and invoice links
Improve collection follow-throughBalance visibility and reviewed remindersBalances and synchronized payments
Support repeat workRelationship history and quiet-client detectionOutreach and later work records
Generate review opportunitiesCompletion-triggered review-request draftsRequests and confirmed outcomes
Improve field prospectingTrips and nearby opportunitiesVisits and resulting conversations
Improve outreach choicesCampaign and template comparisonActual replies and deal outcomes
Improve pricing decisionsJob cost and margin contextRecorded revenue and costs
Preserve organizational capacityLess repetitive preparation and lookupCounted activities and stated assumptions
BASE helps your business work more opportunities, follow through more consistently, and find revenue that might otherwise remain overlooked.

Different economic measures mean different things:

  • Pipeline value is potential revenue.
  • Uninvoiced job value is an opportunity to act.
  • An issued invoice isn’t collected cash.
  • A recorded payment is a financial outcome.
  • A reply isn’t a sale.
  • Activity preceding a win doesn’t prove exclusive causation.

Protect money and margin

  • Flag possible duplicate supplier charges.
  • Surface bills without matching purchase orders.
  • Connect expenses to the jobs they support.
  • Make margin erosion easier to inspect.
  • Catch completed work awaiting billing.
  • Pause or stop inappropriate chasing when payment states change.
  • Reduce duplicate and inconsistent imports.
  • Surface stale connections and uncertain data.
  • Keep draft review and approval visible.
  • Apply usage and processing limits.

A financial finding is a flag for review, not automatically a confirmed loss prevented or cash recovered. Use real outcomes when confirmed, and findings when only flagged.

Save preparation and lookup time

Work whose preparation or lookup effort can be reduced:

  • Sorting inbound messages.
  • Reading routine email to identify its purpose.
  • Finding customer history.
  • Researching businesses and websites.
  • Preparing personalized first drafts.
  • Remembering follow-up timing.
  • Preparing for meetings.
  • Gathering records to answer questions.
  • Comparing options before a difficult decision.
  • Translating spreadsheet columns and values.
  • Detecting repeated or changed imported records.
  • Transcribing supplier documents.
  • Checking documents against playbooks.
  • Reformatting recurring reports.
  • Planning field-sales travel.
  • Assembling activity summaries.
  • Looking for completed work awaiting invoices.
  • Relating costs to margins.
  • Checking connection and automation health.
  • Managing responsibility during staffing changes.

Released capacity can support: customer-facing work, more operating capacity, less administrative pressure, and time away from the business.

An illustrative calculation with explicit assumptions:

If a follow-up normally takes eight minutes to prepare and a prepared draft takes three minutes to review, the illustrative reduction is five minutes per message. Actual results depend on the work and review needed.

A prepared draft isn’t an autonomously completed customer communication. Council or learning activity isn’t itself proof of time saved. Time estimates require explicit activity and review assumptions.

See the value

Catch gaps between related records.

A completed job with no linked invoice deserves a look. BASE flags record mismatches and brings the supporting information into the review.

Cross-system findings

BASE can compare records across feature families to surface missing follow-through and contradictions.

Examples:

  • A job is complete but there is no linked invoice.
  • An invoice is paid but the associated deal is still open.
  • A lead was confirmed but has no recorded follow-up after the configured interval.
  • A supplier bill has characteristics requiring duplicate-charge review.
  • A bill has no matching purchase order.
  • Supplier costs indicate margin erosion.
Your tools each hold part of the story. BASE helps inspect the connections between them.
Cross-system findingConceptual example

Completed job

Work is complete, with recorded value and customer context.

No linked invoice

The configured billing interval has passed without an invoice relationship.

Review item: completed work awaiting billing.

An opportunity to act, rather than a claim of recovered cash.

Uninvoiced-work finding
Uninvoiced-work findingScreenshot placeholder

Completed job, missing invoice relationship, associated value, and operator action.

Screenshot placeholder · Uninvoiced-work finding

Flags versus outcomes

  • Flag possible duplicate supplier charges.
  • Surface bills without matching purchase orders.
  • Connect expenses to the jobs they support.
  • Make margin erosion easier to inspect.
  • Catch completed work awaiting billing.
  • Pause or stop inappropriate chasing when payment states change.
  • Reduce duplicate and inconsistent imports.
  • Surface stale connections and uncertain data.
  • Keep draft review and approval visible.
  • Apply usage and processing limits.

A financial finding is a flag for review, not automatically a confirmed loss prevented or cash recovered. Use real outcomes when confirmed, and findings when only flagged.

Resolve with the supporting records

Inspect evidence, resolve or dismiss a finding, and keep dismissed items out of applicable live totals. Uninvoiced value is an opportunity to act; recorded payment is a financial outcome.

Reporting and receiptsMoney, time, and margin
Payables finding
Payables findingScreenshot placeholder

Supplier bill, job costs, flagged issue, and the supporting evidence.

Screenshot placeholder · Payables finding
See the value

Check what happened, with the records behind it.

Review recorded sends and replies alongside workflow results. Financial findings and time estimates show their supporting records or assumptions, so you can judge what the figures mean.

Reporting and receipts

Review sales and operational metrics, real activity counts, financial findings, stated-assumption time estimates, period statements, weekly narratives, workflow runs, connection health, and usage receipts.

Inspect the work and the supporting records instead of relying on generic AI claims.

Value statement
Value statementScreenshot placeholder

Activity counts, stated assumptions, financial findings, and the reporting period.

Screenshot placeholder · Value statement

Actual activity and stated assumptions

Count actual sends, qualifying replies, stages, outcomes, workflow runs, and recorded failures. Keep system activity distinct from personally credited activity. Time estimates expose their assumptions; usage is distinct from business results.

Workflow receipt
Workflow receiptScreenshot placeholder

Completed or failed work, recorded details, and relevant provenance.

Screenshot placeholder · Workflow receipt

Evidence you can inspect

A value ledger, period statements, and weekly narratives relate reported figures to the supporting context. Financial findings are flags until an outcome has been confirmed.

Money, time, and margin

Look at the preparation your team repeats and the follow-through it sometimes misses. Use your own activity and review-time assumptions to estimate the difference.

Cross-system findings

A completed job with no linked invoice deserves a look. BASE flags record mismatches and brings the supporting information into the review.

Evidence and proof

Use the fictional walkthrough to understand the product, then inspect recorded activity and supporting records when evaluating it in your business.

Connections and control

Connect the tools your business already uses.

Some connections use a native adapter; others rely on files or supported feeds. Check the source coverage and setup requirements for each tool.

Tools and sources

Tool or sourceConnection methodSupported role in BASE
Email providers and inbound servicesSupported SMTP, webhook, and routing configurationInbound triage and approved outbound communication
Google sign-inOIDCUser authentication
Google CalendarCalendar connectionCalendar mirrors and confirmed event creation
Google DriveConfigured shared roots and foldersBrowsing, tracked knowledge, and document ingestion
QuickBooks OnlineRead-only accounting adapterInvoice/payment and supported payables mirrors
CSV and ExcelUpload or pasteReviewed import into declared targets
JSON exportsUpload or supported HTTPS pullReviewed import and repeatable updates
Published spreadsheet/export feedsScheduled HTTPS CSV/JSON pullsSource-specific mirror updates
Website formsSupported lead-intake webhookInquiry capture and supported follow-through
OvertureCatalog ingestion and discoveryBusiness candidates and geographic discovery
Data AxleBusiness-data providerAdditional candidate discovery and review
GeoapifyGeocoding and routingLocation checks and trip calculation
TwilioSMS and voice-event integrationTwo-way texts and missed-call recovery
AI servicesControlled model/tool callsClassification, judgment, drafting, extraction, review, and analysis

Four supported connection patterns: native adapter, supported webhook, reviewed file import, and scheduled supported export pull.

An export-based connection is different from a native API adapter. A booking tool that feeds Google Calendar is different from a direct BASE booking integration. Provider entitlements, account setup, allowed use, consent, and source coverage are part of onboarding.

The core connections don’t include QuickBooks write-back, Outlook, Xero, Stripe payments, universal app compatibility, or MCP support. Future possibilities are described separately where applicable.

Four different connection patterns

  1. Native adapter

    Provider-specific supported access.

  2. Webhook

    Supported configured event intake.

  3. Reviewed file

    Map, match, and confirm records.

  4. Scheduled export

    Reuse approved HTTPS feed formats.

Connection readiness

Accounts, credentials, authorization, provider entitlements, registration, configuration, consent, and source coverage are onboarding requirements. A booking tool feeding Google Calendar is different from a direct BASE booking adapter.

Connection health
Connection healthScreenshot placeholder

Native adapters, setup requirements, synchronization state, and recorded issues.

Screenshot placeholder · Connection health

Health and freshness

Inspect connection state, issues, last relevant runs, scheduled pulls, failures, stale activity, and revoked connections. Where supported, Sync now provides a controlled refresh.

Data and portability

Check mappings and matches before an import lands. Saved source formats can handle repeat updates, while changed formats or unknown values wait for review.

Onboarding

FGH reviews your workflows and current tools before setting up the environment. Imports and prepared work go through review before the agreed workflows activate.

SMS and missed-call recovery

Manage supported business texts with consent records and channel-specific controls.

Connection readiness

Prepare the sources and the responsibilities.

A checklist for the onboarding conversation. Selections stay in this page and are not submitted.

Connections and control

Review incoming data before it changes your records.

Check mappings and matches before an import lands. Saved source formats can handle repeat updates, while changed formats or unknown values wait for review.

Data, imports, and connections

Inspect authorized data through Sheets, Map, Grid, and Table views. Import supported files or pasted data, confirm mappings and matches, review changes, and land approved records in one transaction. Save source-specific formats and manage scheduled export pulls. View connection health, setup requirements, and synchronization results. Add company notes and business-specific custom fields through the data experience.

Reuse existing information without treating unreviewed imports as trustworthy.

Data map and Sheets
Data map and SheetsScreenshot placeholder

Connected records, registered data, agents, applications, and readable tables.

Screenshot placeholder · Data map and Sheets

A reviewed import path

Upload supported CSV, Excel, or JSON, or paste supported data. Choose the target; inspect headers and samples; confirm mappings; review record matches; inspect new, identical, changed, duplicate, and bad data; edit staged values; and land approved records in one transaction.

Controlled data movement

  1. Source

    Inspect headers and samples.

  2. Mapping

    Confirm fields and source values.

  3. Matching

    Review record relationships.

  4. Review

    Inspect changes and exceptions.

  5. Land

    Approve one atomic transaction.

Import review
Import reviewScreenshot placeholder

Mappings, proposed matches, and new, changed, duplicate, or invalid rows.

Screenshot placeholder · Import review

Background synchronization

Save source-specific formats and versioned mappings. Scheduled supported HTTPS CSV/JSON pulls can reuse approved formats. Only qualifying clean feed updates auto-land; changed formats and unknown values park for review.

Historical data

Supported historical imports preserve earlier records without silently waking live workflows. Source references and dated note identity help avoid duplicate or inconsistent records.

Portability

Export supported business Sheets as CSV or JSON, including supported bundles and large streaming exports. Access rules apply to rows and counts; undeclared internal or secret fields remain excluded. Record exports are distinct from a complete database migration package or separately contracted backup access.

Tools and connections

Some connections use a native adapter; others rely on files or supported feeds. Check the source coverage and setup requirements for each tool.

Commercial terms

Talk with FGH about the workflows you need and the service around them. The agreed offer sets pricing and usage limits.

Security and approval

Each client has a dedicated environment. Permissions limit the records people and agents can use, while approval history shows who authorized a communication.

Connections and control

Give people the access their work needs.

Organize the business into units and assign responsibility for its records. Approval authority stays separate from permission to view or work on something.

Teams and responsibility

Organize the business into company, region, location, team, or crew units. Manage memberships, assignments, shared pools, area-specific authority, approval routing, and organizational changes with previews and audit records.

Make who can see, work, approve, and administer information explicit.

Responsibility across the business

  1. Company and units

    Business-specific hierarchy.

  2. People

    Memberships and role bundles.

  3. Work

    Assignments and unit pools.

  4. Approval

    Route to authorized people.

  5. History

    Retain attribution and audit records.

Team access
Team accessScreenshot placeholder

Units, assignments, access scope, and approval responsibility.

Screenshot placeholder · Team access

Who can see, work, approve, and administer

Company, region, location, team, or crew units can be nested. Role bundles and area-specific grants define view, work, approval, and administration authority. Own-versus-all scope, subunit coverage, assignments, and shared pools define the available work.

Approval routing

Route supported approvals to authorized people, with configured ancestor/root fallback and recorded routing. Inspect the access matrix, My access, responsibility counts, pending invites, and units needing approvers.

When people move or leave

Preview the consequences of moving or deactivating a person, reassign active responsibilities, retain historical actor attribution, and record access changes.

Security and approval

Each client has a dedicated environment. Permissions limit the records people and agents can use, while approval history shows who authorized a communication.

Learning

Corrections can lead to a proposed instruction change. Evaluations check eligible changes before approval or guarded automatic application, and version history lets you inspect or undo them.

Connections and control

Keep access and approval explicit.

Each client has a dedicated environment. Permissions limit the records people and agents can use, while approval history shows who authorized a communication.

On this page

Approval in the workflow

Drafting, revision, approval, sending, and receipts are distinct stages.

Human approval stays visible

  1. Prepare

    Draft with relevant context.

  2. Review

    Revise and inspect the version.

  3. Approve

    Record the authorized decision.

  4. Send

    Use the shared outbound path.

  5. Receipt

    Inspect the recorded result.

Configured transactional messages and missed-call workflows have their own defined rules.

Access to your environment

  • Dedicated client isolation

    Each client has its own deployment and database. Dedicated isolation doesn’t eliminate every risk.

  • Identity and sessions

    Sign in with email and password or Google; sessions can be revoked when account circumstances change. BASE uses Argon2id password hashing and signed sessions.

  • Team Units and access

    Define which records a person can use and which communications they can approve. Controls include area-specific access, unit hierarchies, record assignments, own-versus-all scope, approval authority, document grants, and audited organizational changes. Database row-level policies and application checks enforce the access model.

  • Stored connector secrets

    BASE encrypts supported connector credentials and stores the key separately from the database. This protects those connection secrets; it doesn’t mean every field is individually encrypted or that the system provides end-to-end encryption.

Prepared work and agent controls

  • One outbound workflow

    Customer outreach uses the shared draft/approval/send path. Approval is recorded. Explicit allowlisted transactional exceptions include configured lead confirmations and supported operator communications; missed-call behavior follows its channel-specific rules.

  • Controlled agent operations

    Review consequential changes through the applicable confirmation or approval path. Agents use defined tools and registered workflows; custom agents and council seats provide read-only advice. Advice can’t override permissions or send rules.

  • Safe learning

    Review instruction changes and use Undo when a change needs to be reversed. Version history, evaluation gates, and regression safeguards help supervise improvements. Learning changes agent instructions, not the immutable safety rules.

Data handling and accountability

  • External data and website safety

    Supported fetches and imports have boundaries and validation. Third-party text is context, not authority to bypass approval. Template rendering uses controlled structures rather than executing arbitrary model-written templates.

  • Accountability

    Workflow runs, import records, versions, approvals, and access events make relevant activity available for review.

  • Policy and assurance details

    Ask FGH for the privacy and AI processing details, data policies, and operational commitments applicable to your environment.

    QuestionsCommercial terms
What BASE adds

What BASE adds behind the scenes.

Browse the automation and connected workflows that go beyond ordinary manual work in each tool. Every row explains a specific feature.

71 capabilities across 15 categories

Daily operations that surface the next step

4 capabilities

  • One daily review

    Bring decisions, prepared drafts, completed activity, pipeline context, and calendar context into one daily workspace.

  • Revenue attention items

    Surface money-on-the-table findings with links to the supporting records.

  • Daily and weekly briefings

    Receive a configured daily briefing and weekly value narrative.

  • Prepared versus completed work

    Distinguish prepared work from actions that were actually completed.

Email intelligence

5 capabilities

  • Business-specific email triage

    Classify incoming email into your business-specific categories and identify priority.

  • Summaries and information extraction

    Summarize messages and extract configured business information.

  • Connected conversation context

    Link relevant conversations to company records and related work.

  • Inbound interest into sales work

    Turn prospective inbound messages into lead assessments and sales work.

  • Classification feedback

    Use corrections as feedback on eligible classification results.

Prospect discovery and research

5 capabilities

  • Standing market watches

    Run recurring market watches by business type and geography.

  • Lookalike and website research

    Find lookalike businesses and research candidate websites.

  • Evidence-based lead assessments

    Prepare fit scores, supporting evidence, reasoning, and suggested outreach angles.

  • Deeper prospect intelligence

    Add configured website-quality, provider, keyword, advertising, and geographic intelligence.

  • Learning from pursuit decisions

    Learn from eligible pursue/dismiss decisions while preserving human judgment.

Sales follow-through

5 capabilities

  • Context-aware outreach

    Prepare outreach from company context, approved templates, and business voice guidance.

  • Follow-up preparation

    Prepare follow-ups using configurable cadences and timing.

  • Reply-aware cadences

    Pause or halt cadence progression when appropriate, including after a reply.

  • Won deals into delivery

    Hand won work into the Jobs workflow.

  • Observed campaign outcomes

    Compare recorded campaign sends, replies, response timing, and later deal outcomes.

Prepared communications and approval

5 capabilities

  • Grounded first drafts

    Generate a first draft with business context and inspect its provenance.

  • Instruction-based revisions

    Request an instruction-based revision and review the proposed text.

  • Versioned drafts

    Save accepted revisions as versions separately from sending.

  • Recorded approval and sending

    Record outreach approval and send through the shared outbound workflow.

  • Council-informed revisions

    Bring council advice into the normal revision workflow with provenance.

Delivery follow-through

4 capabilities

  • Stale work and billing gaps

    Surface stale work and completed jobs awaiting billing.

  • Lifecycle communication preparation

    Prepare quote nudges, upcoming-work reminders, and completion review requests.

  • Maintenance resurfacing

    Resurface maintenance-related work and connect it to relationship history.

  • Delivery into invoicing

    Hand completed work into the supported invoicing workflow.

Financial checks across records

6 capabilities

  • Payment-aware collection

    Read QuickBooks payment-state changes and stop chasing paid invoices after synchronization.

  • Safe collection pauses

    Pause follow-through for partial payments or stale data and surface attention items.

  • Completed work without invoices

    Compare completed work with invoice links to find overlooked billing.

  • Job costs and margin signals

    Connect supplier costs to jobs and surface margin erosion.

  • Supplier charge exceptions

    Flag possible duplicate charges and bills without matching purchase orders.

  • Evidence behind financial findings

    Inspect evidence behind financial findings without treating flagged amounts as recovered cash.

Docs and approved business knowledge

5 capabilities

  • Approved knowledge for agents

    Bind approved policies, pricing, procedures, and other business knowledge to relevant agents.

  • Tracked Drive knowledge

    Synchronize selected Google Drive files into versioned knowledge.

  • Playbook-based document review

    Review documents against playbooks and retain written reports and history.

  • Reviewed knowledge changes

    Review proposed knowledge changes through the applicable approval path.

  • Branded structured outputs

    Use structured output templates and brand guidance for consistent reports and documents.

Supervised document extraction

4 capabilities

  • Reading scans and supplier documents

    Read supported PDFs, scans, photos, receipts, and supplier documents.

  • Grounded fields and arithmetic checks

    Propose structured fields grounded in source content and check supported arithmetic.

  • Human review before landing

    Stage uncertain results for human review before records land.

  • Controlled document intake

    Process configured supplier attachments and watched Drive folders with volume and source controls.

Assistant with your business context

6 capabilities

  • Business questions with record context

    Ask business questions in a conversational interface, with answers linked to authorized records.

  • Context-aware meeting preparation

    Prepare for meetings using relevant customer, calendar, and operational context.

  • Bounded business analysis

    Analyze financial and operational information through bounded tools.

  • Drafts and confirmed actions

    Prepare communications and initiate supported actions through their confirmation paths.

  • Advisors within the conversation

    Consult custom advisory agents or bring a question to the council.

  • Multi-step assistance

    Plan bounded multi-step assistance and check completion against required deliverables.

Council and custom advisory agents

5 capabilities

  • Plain-language custom advisors

    Define a specialized read-only advisor in a plain-language instruction document.

  • Shared facts across council seats

    Bring a business question to relevant council perspectives using the same authorized facts.

  • Independent views and disagreements

    Collect independent opinions, compare disagreements, and identify missing facts.

  • Recommendations for your decision

    Receive a synthesized recommendation while retaining the operator's decision.

  • Advice returned to the workflow

    Return chosen advice to the originating draft, deal note, review, or Assistant conversation.

Supervised agent improvement

4 capabilities

  • Feedback into instruction improvements

    Connect eligible corrections and feedback to versioned instruction improvements.

  • Controlled learning modes

    Choose learning Off, proposal-only, or guarded automatic improvement.

  • Evaluation and regression checks

    Check changes with evaluations, held-out examples, and regression safeguards.

  • Inspectable changes and Undo

    Inspect changes and Undo supported improvements while preserving code-level safety rules.

Reviewed imports and background synchronization

5 capabilities

  • Suggested mappings and record matching

    Suggest column mappings, translate values, and match incoming rows to existing records.

  • Reviewed data before landing

    Stage new, changed, duplicate, and invalid data for review before landing approved records.

  • Repeatable scheduled imports

    Reuse source-specific formats for scheduled supported CSV/JSON pulls.

  • Clean updates and review exceptions

    Auto-land qualifying clean feed updates and park changed formats or unknown values for review.

  • Connection and run health

    Surface failed runs, stale connections, and other synchronization issues.

Calendar and field preparation

4 capabilities

  • Meeting preparation from business records

    Prepare meetings from calendar context and related business records.

  • Time-budgeted trip planning

    Calculate ordered trip stops using travel time, visit time, and a time budget.

  • Visit-based follow-up

    Find nearby opportunities and prepare follow-up from recorded field visits.

  • Missed-call and lifecycle texting

    Support configured missed-call textback and lifecycle texting with channel-specific controls.

Scoped responsibility and traceable work

4 capabilities

  • Shared access boundaries

    Apply the same relevant access boundaries to people, the Assistant, and agents.

  • Responsibility-based approvals

    Route approvals to authorized people through team and unit responsibility.

  • Staffing changes with continuity

    Preview staffing changes, reassign responsibilities, and preserve historical attribution.

  • Traceable activity and evidence

    Inspect workflow runs, findings, approvals, activity receipts, and stated time-estimate assumptions.

Getting BASE

Set BASE up around your business.

Choose the categories and approved knowledge your team uses, then define responsibilities and workflow limits. Industry configurations provide a starting point.

Business-specific configuration

Categories, approved knowledge, templates, agents, business hours, timezone, briefing preferences, follow-up cadences, branding, integrations, operating limits, outbound identity, trip defaults, and stated ROI rates can be configured around the business. Vertical packs provide starting points rather than replacing business-specific decisions.

Appearance and operating preferences

Supported branding presets, uploaded logos, Light, Dark, or System appearance, and Full, Condensed, or Hidden navigation fit the working environment.

Dark and narrow-screen views
Dark and narrow-screen viewsScreenshot placeholder

Populated supported workflows and appearance preferences.

Screenshot placeholder · Dark and narrow-screen views

Starting points by industry

Owner-led service businesses, teams coordinating work through email and spreadsheets, businesses with useful existing tools but poor connections between them, and companies with repeatable operational work that benefits from shared context.

Existing vertical starting points include software, HVAC, insurance, and financial-advisor configurations. A pack is a configurable starting point, not a regulatory credential or proof of equal maturity in every sector.

Software businesses and BASE.

A configurable starting point built from the same connected capabilities.

HVAC businesses and BASE.

A configurable starting point built from the same connected capabilities.

Insurance businesses and BASE.

A configurable starting point built from the same connected capabilities.

Financial-advisor businesses and BASE.

A configurable starting point built from the same connected capabilities.

Getting BASE

Start with the way your team works.

FGH reviews your workflows and current tools before setting up the environment. Imports and prepared work go through review before the agreed workflows activate.

Understand the work

Describe the actual workflows, decisions, handoffs, current gaps, and desired results. Identify authoritative tools, file sources, accounts, credentials, provider entitlements, and supported connection patterns.

Prepare the environment

Set up the client application and database with the required configuration. Define units, memberships, assignments, approval authority, and document grants.

Review mappings and matches before importing supported historical records. Keep history from silently waking live workflows. Prepare approved policies, procedures, pricing guidance, templates, and agent instructions.

Controlled data movement

  1. Source

    Inspect headers and samples.

  2. Mapping

    Confirm fields and source values.

  3. Matching

    Review record relationships.

  4. Review

    Inspect changes and exceptions.

  5. Land

    Approve one atomic transaction.

Review before activation

Inspect authentication, source coverage, health, and synchronization. QuickBooks onboarding includes a shadow review before live follow-through.

Inspect prepared work, exception handling, approval routing, and operating preferences before activating the agreed workflows.

The delivery offer

Timing, onboarding deliverables, commercial limits, and support commitments are agreed with FGH separately. No instant setup or free trial is implied.

FGH service

FGH helps configure and operate the client environment. The service agreement defines the support and operational commitments for your business.

Commercial terms

Talk with FGH about the workflows you need and the service around them. The agreed offer sets pricing and usage limits.

Tools and connections

Some connections use a native adapter; others rely on files or supported feeds. Check the source coverage and setup requirements for each tool.

Connection readiness

Prepare the sources and the responsibilities.

A checklist for the onboarding conversation. Selections stay in this page and are not submitted.

Getting BASE

FGH’s work around your BASE environment.

FGH helps configure and operate the client environment. The service agreement defines the support and operational commitments for your business.

Supervised operations

Internal support infrastructure helps client provisioning, controlled releases, health monitoring, incident triage, and repair proposals. Internal operators retain approval authority over changes. The internal engineering cockpit isn’t another application clients need to learn.

What the agreement needs to define

Onboarding, support, monitoring, updates, backup and retention arrangements, recovery commitments, and commercial limits belong in the approved business offer. This product description doesn’t establish an SLA.

Explore the existing FGH engagement

Begin with FGH’s workflow audit and engagement process. Discuss the BASE configuration and service that suit your business.

Onboarding

FGH reviews your workflows and current tools before setting up the environment. Imports and prepared work go through review before the agreed workflows activate.

Commercial terms

Talk with FGH about the workflows you need and the service around them. The agreed offer sets pricing and usage limits.

Evidence and proof

Use the fictional walkthrough to understand the product, then inspect recorded activity and supporting records when evaluating it in your business.

Getting BASE

Questions about BASE.

Understand the system, its boundaries, and the information to confirm for your business.

Your business and its records

  • What does BASE do for me on an ordinary day?

    Start with the attention items and prepared drafts in Home. Check the upcoming calendar context, then review the follow-ups or financial findings that need a decision. The fictional day walkthrough shows how different people use that work.

  • Can I keep my current software?

    Yes, where BASE supports the connection. Your existing tool can remain the source of its records while BASE handles related drafts and workflow activity. Check the connection’s setup requirements and coverage before planning around it.

  • Which connections are native and which use files or feeds?

    QuickBooks uses a read-only accounting adapter, while supported calendar and Drive connections have their own setup. Other sources may use webhooks, reviewed file imports, or scheduled HTTPS CSV/JSON feeds. The connections page names the method for each source.

  • What information does BASE store?

    BASE stores customer relationships and the work around them, such as conversations, deals, jobs, and billing context. It also keeps the draft history and approval records created in BASE. The records page lists the full set of record families.

  • Does my company have its own database?

    Each client has a dedicated application deployment and database. Shared context is within that client’s authorized environment.

  • Who can see our records?

    Access depends on the person, area, unit, membership, assignment, document grant, and applicable authority. The Assistant and agents operate through the relevant boundaries.

Approval, advice, and corrections

  • Who can approve communications?

    People with the applicable approval authority can approve supported communications. Unit responsibility and configured routing determine the approval path.

  • Can an agent send a customer message by itself?

    Customer outreach uses the recorded draft/approval/send path. Explicit allowlisted transactional exceptions include configured lead confirmations and supported operator communications; missed-call behavior has channel-specific rules.

  • What happens when it is uncertain?

    Uncertain extraction output can be staged for review. Missing facts, unsupported results, failed runs, and uncertain source data are made available for review in the relevant workflow.

  • Can I inspect and correct its work?

    Inspect supporting records, versions, draft provenance, review history, runs, and receipts. Eligible corrections and explicit feedback support improvements.

  • How do instructions improve?

    Eligible feedback supports instruction proposals or guarded automatic improvements. Versioning, evaluations, held-out examples, and regression safeguards support review.

  • Can I undo an instruction change?

    Supported automatic instruction changes have Undo. Learning doesn’t change code-level safety rules.

  • How do custom agents differ from the Assistant?

    The Assistant is a broad conversational interface to authorized business context and supported actions. Custom agents are specialized read-only advisors defined in plain-language documents.

  • What does a council review actually produce?

    Independent perspectives review common authorized facts and produce options, disagreements, missing facts, and a synthesized recommendation. The operator chooses what to do.

Connections and team changes

  • What happens when a connection fails?

    Connection and workflow health can surface failures, stale activity, revoked connections, and relevant warnings. Review the affected connection and its recorded runs.

  • How current are accounting and calendar mirrors?

    Accounting and calendar views are mirrors. Their freshness depends on the configured synchronization and relevant run results. Inspect connection health and timing rather than assuming instant updates.

  • Does BASE write to QuickBooks?

    QuickBooks is a read-only accounting adapter in the core system. Write-back is a separate future possibility.

  • Can I export my records?

    Supported business Sheets can be exported as CSV or JSON, including supported bundles and streaming exports. Access restrictions apply. This is distinct from a complete migration package or contracted backup access.

  • What is required to activate texting?

    Texting activation requires the supported provider workflow, account configuration, registration, consent/opt-out controls, and channel gates as part of onboarding.

  • What happens when an employee moves teams or leaves?

    Preview a move or deactivation, reassign active responsibilities, preserve historical actor attribution, and record access changes.

Value and external AI processing

  • How is time saved estimated?

    Use counted activities and stated assumptions about preparation and review effort. A prepared draft isn’t a completed customer communication, and an advisory run doesn’t itself prove time saved.

  • How are financial findings distinguished from recovered money?

    A financial finding is a flag and an opportunity to investigate. Only a confirmed financial outcome can support a recovery claim. Keep pipeline, uninvoiced work, invoices, and payments distinct.

  • What reaches an external AI provider?

    Ask FGH for the processing disclosure covering the AI providers configured for your environment.

Data policies and the service

  • What are the retention and deletion policies?

    The retention and deletion policies applicable to your environment are part of the service terms. Ask FGH for those details.

  • How are backups and recovery handled?

    Ask FGH for the backup arrangements and recovery commitments applicable to your environment.

  • What does onboarding require?

    Discovery, a tool inventory, a dedicated environment, team/access setup, historical imports, knowledge preparation, connection validation, and a review period. The offer defines delivery commitments.

  • What support is included?

    Support coverage and commitments depend on the agreed service. FGH can explain the scope for your business.

  • What are the usage and commercial limits?

    FGH will discuss pricing, usage limits, and commercial terms for your business. Recorded usage measures activity; it doesn’t define the pricing model.

Getting BASE

Discuss the service and its terms.

Talk with FGH about the workflows you need and the service around them. The agreed offer sets pricing and usage limits.

Pricing and usage

Discuss the workflows and service your business needs with FGH. Pricing and usage limits are set out in the agreed offer.

Support and operational commitments

FGH can explain the support coverage and operational arrangements available for your environment. The agreement defines the applicable commitments.

Your data and exports

Supported record exports are described in the data chapter. A complete database migration package and backup access are separate arrangements.

Data and portability

Check mappings and matches before an import lands. Saved source formats can handle repeat updates, while changed formats or unknown values wait for review.

FGH service

FGH helps configure and operate the client environment. The service agreement defines the support and operational commitments for your business.

Getting BASE

Check the work behind a result.

Use the fictional walkthrough to understand the product, then inspect recorded activity and supporting records when evaluating it in your business.

Explore a connected business day

Follow Cedar Service Company, a fictional business, through the daily walkthrough. The example shows how the work connects; it represents an illustration rather than a customer result.

A day with BASE
Home workspace
Home workspaceScreenshot placeholder

Attention items, prepared drafts, completed activity, calendar context, and useful totals.

Screenshot placeholder · Home workspace

Inspect the work behind a result

A prepared draft shows preparation; a confirmed payment shows a financial outcome. Review the activity behind each figure before treating it as a business result.

Reporting and receipts

Review recorded sends and replies alongside workflow results. Financial findings and time estimates show their supporting records or assumptions, so you can judge what the figures mean.

Money, time, and margin

Look at the preparation your team repeats and the follow-through it sometimes misses. Use your own activity and review-time assumptions to estimate the difference.

Evaluate it around your business

Discuss your current process and the outcomes you want to measure with FGH. A relevant demonstration starts with the work your team actually does.

Future possibilities

Ideas beyond the current system.

These possibilities aren’t working parts of BASE today. They have no committed dates.

On this page

  • Customer conversion and payments

    • Public quote approval with line items.
    • Deposits at approval.
    • Invoice payment links.
    • Client-owned Stripe payment integration.
    • Card and ACH payment options.
    • A customer portal.
    • E-signature workflows.
    • Recurring and retainer invoicing.
    • Maintenance agreements.
    • Financing partner integrations.

  • Communications and reputation

    • Gmail API onboarding without forwarding/routing setup.
    • Outlook mail and Microsoft calendar adapters.
    • Expanded review-request sequences.
    • Google Business Profile review ingestion.
    • Human-approved public review responses.
    • Voicemail transcription and triage.
    • Immediate hot-inquiry operator alerts.
    • Bilingual customer communications.
    • Event-triggered social drafts.

  • Scheduling and identity

    • Reliable calendar-to-record linking.
    • Job-update proposals from linked event completion.
    • Optional hosted booking.
    • Deeper person/contact identity.
    • Broader email/phone normalization.
    • Customer-contact deduplication.

  • Financial intelligence

    • QuickBooks write-back.
    • Xero support.
    • A cash-flow snapshot.
    • Core-credit recovery.
    • Line-level price/quantity discrepancies.
    • Expanded unbilled-cost detection.
    • Pricing and quote intelligence.
    • Estimate-to-materials-to-draft-PO workflows.
    • Warranty and callback costs.
    • Job-cost imports with appropriate date, identity, and access modeling.

  • Analytics and customer-facing intake

    • Broader structured business analytics.
    • Read-only advertising attribution.
    • Website lead-capture widget.
    • Knowledge-grounded customer webchat.
    • PWA improvements.
    • Push notifications.
    • Expanded website checks for forms, dead links, certificates, and public hours.
    • Consolidated compliance/approval exports.

    MCP, third-party Agent Skills, Word export, and cross-client learning aren’t part of the current core-system claim. Any future expansion would be a separate product decision.

  • Separate product decisions

    MCP, third-party Agent Skills, Word export, and cross-client learning aren’t part of the core-system claim. Any reconsideration is a separate product decision.

Explore it around your business

See how BASE fits your business.

Bring a workflow your team handles today. We’ll look at where BASE can help and what your team would still review.