Maru Systems · the catalog

Six agents on the shelf.Anything else is quoted.

An agent joins this catalog once it runs in production. Each listing states whether it is running, ready in ten business days, or a first build scoped on its own timeline, and what is out of scope is printed next to what is in.

Front Desk

First build, scoped

Answers your phone, qualifies the caller, books the appointment, logs it.

$6,500

first build, scoped individually: 15 to 20 business days

Care from $1,000/mo

agents/front-desk
bookaskescalateCall inTwilio VoiceTranscribestreaming STTAI AgentTools AgentSwitchmode: RulesCalendaravailabilityHold slotidempotentConfirmvoice + SMSAnswerknowledge baseWrite CRM+ transcriptRing humanescalationModelMemorycaller historyCalendarCRM

▸ Swipe the diagram. Front Desk · a live listing, not an illustration.

Connects to

  • Twilio Voice
  • Google Calendar, Outlook or Cal.com
  • HubSpot, Pipedrive, Salesforce, Jobber or ServiceTitan
  • Slack or SMS for escalation

In scope

  • One phone number, one language
  • Your services, hours and pricing as the knowledge base
  • Up to three booking types
  • Human escalation path
  • Recordings and transcripts retained in your account

Out of scope

Outbound calling campaigns, payment capture over the phone, additional languages, and IVR trees deeper than two levels. Each quoted separately.

Technical detail+

Streaming speech-to-text with sub-400ms partials. Intent classification runs against a constrained schema, so the model cannot invent a service you do not offer. Calendar writes are idempotent and keyed on the call SID, so a retry never double-books. Every recording lives in your own storage bucket. It fails to a human, never to a dead end.

Intake

Running here

A form that qualifies the lead and books it, instead of just collecting it.

$3,500

running here · in production in 10 business days

Care from $600/mo

agents/intake
bookwarmno fitForm / SMSweb · keywordQualifyTools AgentScoreexplicit rubricSwitchmode: RulesHold slotshort TTLConfirmemail + SMSCRM+ transcriptNurturesequenceDeclinepolitelyModelThreadCalendar

▸ Swipe the diagram. Intake · a live listing, not an illustration.

Connects to

  • Your website
  • Cal.com, Google Calendar or Outlook
  • Your CRM
  • Resend or your email provider
  • Twilio for reminders

In scope

  • One intake flow
  • Your qualification rules
  • Three routing outcomes
  • Confirmation and reminder sequence
  • CRM record including the full transcript

Out of scope

Payment or deposit capture, multi-step approval chains, and quoting. Each quoted separately.

Technical detail+

Qualification runs against an explicit rubric rather than model judgement alone, so every routing decision is auditable and you can see exactly why a lead was declined. Slots are held with a short TTL and released on abandonment, so your calendar never fills with ghosts.

Reconcile

First build, scoped

Keeps two systems that don't talk in agreement, continuously.

$6,500

first build, scoped individually: 15 to 20 business days

Care from $1,000/mo

agents/reconcile
matchmismatchruleabove capScheduleevery 15 minFetch AShopifyFetch BQuickBooksNormalizecommon shapeDifffield-levelSwitchmode: RulesLogaudit trailClassifyTools AgentAuto-resolveunder thresholdExceptionto a humanModelRulesHistory

▸ Swipe the diagram. Reconcile · a live listing, not an illustration.

Connects to

  • Shopify
  • QuickBooks or Xero
  • NetSuite or Business Central
  • Square or your POS
  • Direct SQL against your database

In scope

  • Two systems, one entity type
  • Inventory, orders, customers, invoices or payments
  • Your resolution rules
  • Exception queue with recommendations
  • Daily summary and a full audit trail

Out of scope

More than two systems or more than one entity type per build, and historical backfill beyond twelve months. Each quoted separately.

Technical detail+

Every write is idempotent and reversible. Every automated resolution is logged with the rule that fired. Nothing auto-resolves above a value threshold you set: above it, the case goes to a person with the evidence attached. This is the agent most likely to touch money, so it is built to be audited rather than trusted.

Chase

Follows up on invoices and estimates until they're paid or declined.

$4,500

in production in 10 business days

Care from $600/mo

agents/chase
yesdisputeInvoiceissued · overdueSequenceage + amountDraftin your voiceStill owed?checked at sendSendemail · SMSReplyinboundClassifypaid · disputeEscalateto youModelTone samplesLedger

▸ Swipe the diagram. Chase · a live listing, not an illustration.

Connects to

  • QuickBooks, Xero or Stripe
  • Resend or your email provider
  • Twilio
  • Your CRM

In scope

  • One sequence for invoices, one for estimates
  • Tone calibrated to samples you provide
  • Reply classification and escalation rules
  • Stop-on-payment
  • Weekly recovery report

Out of scope

Collections beyond ninety days, legal escalation, and payment plan negotiation.

Technical detail+

Stop-on-payment is checked immediately before every single send, not on a schedule, because the fastest way to lose a client is to dun someone who already paid. Every outbound message is logged against the invoice it belongs to.

Brief

The numbers you can't see until the 15th, in your inbox every Monday.

$3,500

in production in 10 business days

Care from $600/mo

agents/brief
ScheduleMon 06:00POSsalesAccountingmarginCRMpipelineNormalizeone shapeComputevs prior · targetAnomaliesstatisticalWrite brieffrom figures onlyEmailMon 07:00Dashboardlive linkModelSchemaLast week

▸ Swipe the diagram. Brief · a live listing, not an illustration.

Connects to

  • Your POS
  • Accounting
  • CRM
  • Calendar and ad platforms
  • Anything with an API or a database

In scope

  • Up to five sources
  • Your KPI definitions
  • One weekly email
  • One live dashboard
  • Twelve months of history where the source allows

Out of scope

Forecasting, board-grade financial reporting, and custom BI modelling.

Technical detail+

Every number on the dashboard is traceable to the query that produced it. The narrative is generated from the computed figures, never from the model's own arithmetic, so it cannot invent a number. Anomaly flags are statistical rather than vibes-based, and the thresholds are yours.

Callback

Waitlist

A missed call becomes a text conversation in under sixty seconds.

$3,500

waitlist: opens when carrier registration clears

Care from $600/mo

agents/callback
readycomplexMissed callstatus callback60s timerdebouncedSend SMSsame numberQualifyTools AgentSwitchmode: RulesBookcalendarRouteto a humanNotify + logCRMModelPer numberCalendar

▸ Swipe the diagram. Callback · a live listing, not an illustration.

Before it can shipRequires A2P 10DLC carrier registration before it can send. Registration takes roughly two to three weeks and we start it during scoping.

Connects to

  • Twilio Messaging, 10DLC registered
  • Your calendar
  • Your CRM

In scope

  • One number
  • Business-hours and after-hours message variants
  • Qualification against your rules
  • Booking
  • Opt-out handling and compliance

Out of scope

Marketing broadcast, multi-number pools, and MMS.

Technical detail+

Conversation state persists per phone number on a rolling window, so a caller who replies three hours later is not greeted from scratch. Hard stop on STOP keywords. Rate limited per number so a loop cannot form.

Not on the shelf?

Most of what gets built here starts as a custom quote and earns its place in the catalog later. Bring the workflow that is eating your week and we will scope it honestly, with its own timeline rather than a ten-day promise it cannot keep.

Book a fit call