Example project

Example project: document and inbox automation for a small distributor

How we would take repetitive typing and inbox sorting off the team of a ten-person distribution company near Milwaukee, with a person checking every result.

Example project, not a real client. The business, the situation and every detail below are invented to show how we would plan and measure this kind of work. This page has no results, quotes or testimonials, and every price comes from our published list.

At a glance

The business (invented)A ten-person wholesale distributor that sells to contractors and shops
AreaThe Milwaukee area
Starting pointPurchase orders and invoices arrive as email attachments and are typed into a spreadsheet by hand. A shared inbox takes the office manager an hour or more a day to sort
Services usedAn AI review of how the team works, then the Manage plan
FeesManage is $349 a month with a one-time setup that starts at $799. Build work is quoted by task on our pricing page before it starts.
After that$349 a month to keep the automations running and improving

The situation (invented)

The office manager and one sales assistant spend part of every day typing order details from documents into a spreadsheet and sorting incoming mail into who should answer it. Mistakes are rare but costly, and when either person is away the backlog grows.

The owner is interested in AI but wants to keep a person in charge, and does not want customer data sent to tools nobody has checked.

The goals

  • Take the typing out of one document type first, and measure whether it works.
  • Sort the shared inbox into clear categories and draft replies for a person to review.
  • Keep a person approving every output, with simple records of what the tools did.
  • Document everything, so the team owns the result.

What we would do

Week 1: understand the work

Map the current steps with the people who do them: where documents arrive, what gets typed, how long an item takes, where mistakes happen. Choose one task that is frequent, simple and well defined.

Weeks 2 and 3: build and test

Build a workflow that pulls the needed fields from one type of order document into the spreadsheet, and an inbox assistant that sorts messages and drafts replies. Test on real past examples and show the results to the team before anything is installed.

Week 4: pilot with a person in charge

Run the workflow on live work with a person approving every output. Record what needed correcting, and fix the causes.

Day 30 and after: review

Compare against the starting measurements and decide with the owner: expand, change, or stop. If the Manage plan is chosen, we keep the workflows running and improve them.

What the client would get

  • A document workflow for one order document type, with a person approving results
  • An inbox assistant that categorizes messages and drafts replies for review
  • Plain documentation of what each workflow does, what it touches and how to turn it off
  • A simple log of corrections, used to improve the workflows
  • A 30-day review with a clear recommendation

How we would measure it

This is the layout of the monthly report we would share. It holds no data, because this is an example.

MetricHow it is countedStarting pointTarget
Items handled by the workflowWorkflow logZero at the startGrows week by week
Share of outputs a person had to correctReviewer's correction logNot applicable at the startFalls over the pilot, with causes fixed
Time per item, before and afterStaff time a sample of items before the pilot and during itMeasured in week 1Lower, using the team's own measurements
Inbox messages sorted and draftedInbox assistant logZero at the startReviewed with the office manager
Errors that reached a customerThe owner's recordsCounted from the startNone, which is why a person approves outputs

What a good result looks like

A good 30 days is not a promise of hours saved. It is one workflow that works on real documents, a person who trusts it because they approve every result, honest records of what needed fixing, and a clear decision about what to do next. We measure time with the team's own samples and we do not quote savings we have not measured.

What we would need from the owner

  • Time with the people who do the work, to map it accurately
  • A set of past documents and emails to test on, with a decision on what customer data may be used
  • A named reviewer who approves outputs during the pilot
  • Agreement on which tools may touch customer data, checked against their terms

Plans and prices

Every fee above is on our pricing page. The service behind this example is AI and automation. You own your accounts, domains and data, and we do not guarantee leads, rankings or mentions in AI answers.

About this example. We have not published client results because we would rather show our process than invent numbers. When we have client work to share with permission, it will appear here as real case studies.

Not sure what you need?

Take the survey to find out exactly what your business needs.

Seven quick questions, about two minutes. We recommend a package and write your message for you. A person replies within 2 business days.

Take the survey
Ready when you are

Have something to grow?

Tell us what you are working on and where you want it to go.

We reply within 2 business days.

Say hello
↗