Skip to content
SGF

Capacity. Planning is open. Company implementation is full — join the waitlist.

Join the waitlist

Services

What we sell.

Inbox, Ops, Follow-up on one shared computer. Grok Bot first — dealerships and the trades. Grok, Claude, ChatGPT. Planning is open. Implementation is waitlist-only.

  1. 01

    Grok Bot setup

    Inbox, Ops, Follow-up. One computer. The human is not the middleman.

    Grok Bot is xAI’s always-on agents. One bot, one job. Three bots run three jobs at once on a shared cloud computer. They pass files and records. They message each other. Signed into Airtable, HubSpot, Slack, the inbox, meeting notes. We do not rip out what works. Then we show the team the handoff so they spend hours making money.

  2. 02

    Founder and operator setup

    When one person is still the bottleneck — and the company will grow.

    From a single operator to the first team. Models, meeting notes, and a source of truth built so it does not collapse when headcount and volume show up. Not a toy stack for a side project.

  3. 03

    AI agent setup

    Agents that work in your systems, not next to them.

    We map the jobs that should not be a human swivel-chair, then design agents that file, route, draft, update, and follow up. Evaluation, fallback, and a person who owns it — not a chatbot bolted onto the homepage.

  4. 04

    Data architecture

    The source of truth — Airtable, or what you already run.

    Schema, relationships, interfaces, and automations. Airtable when it is the right base; SmartSuite, Coda, Monday, ClickUp, or Sheets when that is already the record. London specialists on Airtable. We do not start by ripping out a working system.

  5. 05

    Apps and portals

    The software your team and clients actually use.

    Noloco, Softr, Glide, or Stacker on top of the data. Roles, workflows, branding. Our London partners are among the strongest Noloco operators in the field — and we work in the app layer you already paid for.

  6. 06

    Notion operating system

    Process your people and your agents can both follow.

    Notion or Confluence. Structure, owners, and a place for the current way of working. If it is not in the wiki or the base, it is not the process.

  7. 07

    Connect the stack

    The CRM, the store, the helpdesk, the glue — and the alternatives.

    HubSpot or Salesforce or Pipedrive. Shopify or Woo. Zendesk or Gorgias. Zapier, Make, or n8n. Meeting notes from Granola, Circleback, Fireflies, Fathom, or Otter. Connected to whatever is the source of truth — Airtable or not. We do not rip out what already works.

  8. 08

    Training and handoff

    A system your team can run without us.

    We show the team how Grok Bot takes the busy work. Docs, office hours, and a cadence. Then they own the handoff.

  9. 09

    Private in-home AI servers

    Coming soon. Your own box. Your data stays home.

    A private server in the home or on-site that runs the company’s AI so customer lists, quotes, and files never leave the building. Same jobs we set up on Grok, Claude, and ChatGPT — on hardware you own. Not for sale yet. Join the waitlist.

What we actually install

Three named agents. One shared computer.

Grok Bot is xAI’s always-on agents. One bot, one job. Three bots run three jobs at once. They share a cloud computer. They pass files and records. They message each other. You are not the middleman. You spend the hours making money.

  • One bot, one job

    Inbox. Ops. Follow-up. Not one chatbot pretending to be the company.

  • They run at the same time

    Three jobs, one computer. A lead does not wait for someone to copy it from mail to the base.

  • They pass the work

    Files, records, a short message between bots. The human is not the swivel-chair.

  • Signed into what you already run

    Airtable, HubSpot, Slack, the inbox, meeting notes. We do not rip out what works. Outbound stays a draft until a named yes.

Typical first three

  1. Inbox

    Mail and forms become records. Qualify. Route. Draft the first reply.

  2. Ops

    Dispatch, exceptions, the book. Real capacity. Emergencies escalate.

  3. Follow-up

    The next text, the next RO, the declined estimate. Draft until a named person says send.

Where AI actually helps

Intake. Qualify. Book or request. Escalate.

We sell an operating system — role contracts, named-yes gates, a 90-day sequence, weekly coaching. Not AI employees that replace staff. We do not stand up a full AI OS on day one.

  1. 01

    Intake

    Answer the call, the form, the after-hours overflow.

  2. 02

    Qualify

    Scripted questions. Live inventory or real capacity — not a guess.

  3. 03

    Book or request

    Write the appointment or the request into the system you already run.

  4. 04

    Escalate

    Negotiation, emergencies, complaints — a named person takes it.

Outbound SMS and email need a named human yes. Inbound answer and book stays inside approved scripts.

An empty dealership service lane at night, one sedan, cool overhead light.

Sales · BDC · service · inventory

Car dealerships

Internet leads, missed calls, and service status — written back to the CRM or DMS. People keep negotiation and complaints.

  • After-hours and overflow inbound

    Qualify, then book a test drive or a service visit.

    The call or form lands in the CRM or DMS. After hours and overflow do not die in voicemail.

  • First reply on internet leads

    SMS or email with live inventory and guardrailed pricing.

    Negotiation and complaints escalate to a person. The bot does not make a deal.

  • Fixed-ops missed-call rescue

    Repair-order status on one customer record.

    A missed service call becomes a write-back, not a second sticky note.

  • Service retention drafts

    Declined service, recall, or a lapsed VIN — as a draft.

    Outbound only after a named human yes. Nothing sends itself.

An empty trades shop at dusk, a work van at an open bay, copper pipe on a steel table.

HVAC · plumbing · electrical · roofing · GCs

Plumbers and the trades

After-hours voice, dispatch, estimates, and inbound SMS — booked against real capacity. Emergencies escalate by keyword.

  • After-hours and overflow voice

    Book against real capacity, or open a request.

    Emergency keywords go to a person. Everything else becomes a job or a request in the board.

  • Call and text receptionist

    Schedule an estimate or a job, escalate, or text back after a hang-up.

    Hang-up texts stay drafts until someone approves them.

  • CSR that books the calendar

    Real hours, real services, real availability.

    It does not invent a slot. If the book is full, it waitlists or opens a request.

  • Estimate and declined-work follow-up

    Drafts only.

    Never auto-send. A named yes is the gate.

  • Waitlist

    The bot may add a name and draft “a slot opened.”

    The send waits for a named human approval.

The operating system

  • Role contracts

    Each bot has a job, a script, and tools. It does not wander the company.

  • Named-yes for outbound

    SMS and email campaigns stay drafts until a named human says yes. Inbound answer and book stays inside approved scripts.

  • Ninety days, not day one

    One pilot. Then booking rules. Then optional outbound. We do not stand up a full AI operating system on day one.

  • Weekly coaching

    Your people keep the work. We coach the handoff. This is not AI employees replacing staff.

Shapes of work

Typical builds

  • Grok Bot for the team

    Inbox, Ops, Follow-up on one shared computer. They pass files and records. They message each other. The team is not the swivel-chair. Hours go back to making money.

  • Operations at volume

    Dispatch, exceptions, and handoffs that already hurt at company scale. Agents watch the base, draft the next action, and write back. Noloco is what the field and the office see.

  • HubSpot to operations

    Leads and deals leave HubSpot as work: qualified, written into Airtable, visible in Noloco. Agents log activity so sales and ops stop living in two systems.

  • Multi-system rollout

    HubSpot or Salesforce, Airtable, Noloco, the meeting layer, and the models — one operating loop. Built for volume, permissions, and more than one owner.

  • Client delivery portal

    Clients stop living in your inbox. A Noloco portal on Airtable, with Notion as the policy the agent is allowed to quote.

  • Weekly operating brief

    Grok or Claude reads the live bases and the Notion log, then files a brief a founder can actually use on Monday.

  • Intake to record

    Leads, tickets, or requests land once — qualified, routed, and created as records. No retyping.

Join the waitlistBuild a plan

Start

Three named agents. One shared computer.

Inbox, Ops, Follow-up. They pass the record. You are not the middleman. Planning is open. Implementation is waitlisted.

Get a company planTalk to us