For small businesses with more work than people

Custom tools for problems off-the-shelf apps miss.

Every small business has work no app quite fits: quote requests in your own format, invoices from forty vendors, answers buried in your policy folder. We build an AI tool for your version of the problem, inside the software you already use, and nothing goes out until someone on your team approves it.

Ridgeway HVAC / Leads / Brightline Dental Waiting for approval

Inquiry · 9:14 am

Hi, our two office AC units need servicing before July. Could someone come out next week? We're at 410 Alder St.
Dana Ruiz

Details pulled out

Contact
Dana Ruiz
Service
AC service 2 units
Site
410 Alder St.
Timing
Next week
Missing
Make and model

Reply drafted for review

Hi Dana, thanks for reaching out. We have openings Tuesday and Thursday morning next week for both units. Could you send the make and model from each unit's label? That way the tech brings the right filters.
Marcus, Ridgeway HVAC

Also updates the CRM: stage "Contacted"

What we build

Built around your problem, not a template

We start with the task that costs your team the most time and design a tool for it. Here are a few examples of what that can look like. Yours will probably be different, so bring it to the review call.

Lead replies

Every inquiry gets a drafted reply and a CRM entry within minutes, including evenings and weekends.

Shown below

Invoice and document processing

Invoices, intake forms and receipts become clean records, with missing details flagged.

Shown below

Staff answers

Staff ask questions in chat and get answers from your own policies, with the source attached.

Shown below

Appointment reminders

Confirmations, reminders and no-show follow-ups drafted from your calendar.

Scoped on request

Review requests

Customers get a well-timed request for a review after a job is marked complete.

Scoped on request

Weekly summaries

A plain-language summary of leads, jobs and unpaid invoices, pulled from the tools you use.

Scoped on request

Examples

Three examples, shown working

See what goes in, what comes out, and where a person checks the work. Each example includes something going wrong, like a missing address or a missing PO number.

Clearday Commercial Cleaning / Quote requestsInbox · HubSpot · Calendar

Goes in · web form, Sat 11:42 pm

Looking for a quote on weekly cleaning for our 3,200 sq ft office. We'd want to start in two weeks.
Theo Park

Comes out

Hi Theo, thanks for getting in touch. For a 3,200 sq ft office, weekly cleaning usually takes one crew about 3 hours. Could you send the address and which weekday suits you? I'll send a written quote by Tuesday. Priya

CRM
New deal
Task
Quote due Tue

A person checks

Priya sees the draft Monday at 8 am, edits it if needed, and clicks send. Nothing reaches a customer without approval.

Exception handled. No company name or address in the form. The draft asks for them instead of guessing, and the CRM record is marked incomplete.

Measured in a pilot: time to first response, minutes per inquiry, share of drafts sent with few or no edits.

Demonstration project

Weekend quote follow-up for a landscaping crew

Situation
A 9-person landscaping company gets most quote requests on weekends, when no one is at a desk.
What was built
Form and email requests land in one queue, each with a draft reply and a CRM entry, ready on Monday morning.
How it was tested
40 sample requests, including 6 with missing addresses or unclear services, each checked against an expected result.
What stays manual
Pricing and scheduling. The tool asks for missing details; a person decides the quote.
Greenway Landscaping / Quote requestsDemonstration
ReceivedRequestStatusDrafted in
Mon 7:52 amHedge trimming, 2 propertiesOakmont HOADraft ready4 min
Mon 7:31 amSpring cleanup quoteJ. AlvarezSent3 min
Sun 9:15 pmIrrigation repairNo address givenNeeds info5 min
Sun 2:40 pmWeekly mowing, Apr–OctGreenleaf DentalSent4 min
Built with fictional data. Not a customer deployment.

How to start

Start with one tool

We pick the tool your business needs most and agree on what "working" means, then build it as a paid pilot. If it does the job, you keep it. If you want more, we scope the next one.

Book a free review

Scope

  • One tool with named inputs and outputs
  • Up to two connected tools, such as your inbox and CRM

You receive

  • A working tool in your accounts
  • Test results on agreed examples
  • Written documentation
  • A walkthrough with your staff

Done means

  • It handles a set of real examples agreed in advance
  • Including the awkward ones: missing fields, odd formats, unclear requests

We'll need from you

  • Access to the relevant tools
  • 20 to 50 sample items
  • One reviewer, about 2 hours a week

Not included

  • Replacing your existing software
  • Training a model from scratch
  • Anything that sends money or messages without a person approving it

Process

What happens, and what we need from you

30 minutes, free

1. Review call

We talk through the task, how often it happens, and which tools it touches.

You: describe the task and who does it now.

About 1 week

2. Scope and quote

A written scope: inputs, outputs, test examples, price, and exclusions.

You: share samples and approve the test set.

2 to 4 weeks

3. Build and test

We build in your accounts and run the agreed examples. You see results weekly.

You: review results and flag anything wrong.

Ongoing

4. Launch and support

Staff walkthrough and documentation, then monitoring and fixes.

You: name who reports problems.

Pricing

What you pay up front, and what continues

Three separate costs, each in writing before any work starts.

CostWhenCoversPrice
Pilot buildOne timeScoping, build, testing, documentation and walkthrough. Fixed once scope is agreed.from $1,500
SupportMonthly, optionalMonitoring, bug fixes, adjusting to changes in your tools. Cancel with 30 days' notice.$300 / mo
Model and software feesUsage, at costAI model usage paid to the provider, plus any new subscriptions, in your name where possible.$20–$150 / mo

What changes the quote

  • How many tools need to be connected
  • Whether those tools can be connected directly
  • How varied the inputs are: one invoice layout or forty
  • How many exceptions need their own handling
  • Change requests after scope is agreed, quoted separately
Sample engagement: weekend quote follow-up, 9-person landscaping company Connects a web form, Gmail and HubSpot for about 60 requests a month. Build $2,500 over 3 weeks, support $300 / mo, usage about $30 / mo.

Control and reliability

You stay in charge of what it does

Data access

The tool gets access only to the accounts and folders the workflow needs. You can revoke it at any time.

Approvals

Anything sent to a customer or posted to your books waits for a person to approve it, unless you decide otherwise in writing.

Testing

Before launch, it runs against the examples we agreed on. You get all the results, including the ones it got wrong.

When it fails

Unclear or incomplete items are flagged for a person instead of guessed. Errors are logged and we're notified.

Ownership

The tool runs in your accounts. You own the code, prompts and configuration, and keep them if we stop working together.

Which AI

Most projects connect an existing model, such as Claude or GPT, to your documents. Nothing is trained on your data. If a project needs more, the scope says so.

Who builds it

Engineers from big tech

the people you'll talk to are the ones who build it

Custody's team is made up of software engineers who have worked at big tech companies such as Meta and Amazon. There we built internal tools that teams used every day, and saw how much time a small fix to a repetitive task can save. Custody does the same for small companies without an engineer on staff.

Questions owners ask

Will it work with the software we already use?

Usually. Common tools like Gmail, Outlook, HubSpot, QuickBooks, Google Drive and SharePoint can be connected. If one of yours can't, we'll tell you on the free review call, before you pay anything.

What happens to our data?

It stays in your accounts. It is sent only to the AI provider that processes it, under business terms that keep it out of model training. The privacy and data handling page has the details.

What if the AI gets something wrong?

It will sometimes. That's why outputs go to a person for approval, unclear items are flagged instead of guessed, and testing includes the awkward cases. Under the support plan, we fix recurring mistakes.

How much does it cost?

A one-time build fee, an optional monthly support fee, and usage fees passed through at cost. The pricing section shows starting points and what changes the quote.

How long does a pilot take?

Usually 3 to 5 weeks from agreed scope to launch, depending on how quickly we get access and sample data.

What support do we get afterwards?

The optional support plan covers monitoring, bug fixes, and adjustments when your tools change. New workflows are quoted separately.

What do we keep if we stop working together?

Everything: the running tool, code, prompts, configuration and documentation. It's already in your accounts, and we'll hand over any remaining access.

Free review

A 30-minute call about the job that eats your week

What we'll cover:

  • What the task is and who does it now
  • How often it happens and how long it takes
  • Which tools are involved
  • Whether a tool would actually help

Afterwards you get a short written summary. If a pilot makes sense, we'll send a scope and price within a week. If it doesn't, we'll tell you.

You'll speak with an engineer who would build your tool. No sales team, no handoff.

Any email address works, including Gmail. It's used only to arrange this call.