BedrockProcess

AI automation for owner-run businesses

I build AI systems that take the busywork off your team.

I work with owner-run companies that have been around a while and still run on email and PDFs, with people retyping the same information into the system every day. We pick one job that eats hours every week, I automate it, and we measure the hours it saves before we talk about anything bigger.

Dan Wilson, founder of Bedrock Process
Dan Wilson Founder, Bedrock Process Builds production AI agents full-time

What order entry automation looks like

The most common place to start. A customer emails a purchase order as a PDF, and instead of someone typing it into your ERP line by line, the system reads it and stages a draft order for your team to check.

Illustration with sample data.

Where it usually starts

The best first job is one your team does every day, by hand, with clear rules.

  • Orders that arrive as emails and PDFs

    Someone reads each one and types it into your ERP. The system does the typing and matching, and that person approves the draft.

  • Quotes that never got a follow-up

    A daily list of the open quotes worth chasing, with the follow-up email already drafted for the rep.

  • Vendor invoices matched by hand

    Invoices checked against purchase orders and receipts, with only the mismatches sent to a person.

  • The numbers you have to ask for

    Margin by customer, rep and product, pulled from data your systems already hold and in front of you every morning.

Work I've shipped

Different industries, same job: find the work people repeat by hand, build the system that does it, and measure the result.

Enterprise AI program · my full-time role

A stalled AI rollout in a large company's sales organization

When I took it over, 2 people a week were using it. The tool didn't know how the business worked, and the agents were wrong often enough that nobody trusted them. I fixed those causes first: taught the system the company's data, org structure and vocabulary, and rebuilt the most-used agents. Then I trained people one on one and built a champion network that meets weekly. I now build and run the company's production agents across sales, trust and safety, and customer success.

2 → 88
weekly users of 112 seats, in 60 days
28
production AI agents
65%
faster on the most-used agent
3.6x
program ROI against license cost

Operations platform · owner-run brokerage

A transaction portal for a flat-fee real estate brokerage

The brokerage ran hundreds of open deals on spreadsheets, email threads and manual status tracking, and deals got lost. I designed and built one system for all of it: listing intake, state-by-state compliance tracking, task assignment, payments and e-signatures, and revenue reporting.

6 weeks
from scope to launch
1,900+
homeowners listed in the first 18 months, across 4 states

Research and outreach pipeline · 12 B2B clients

Prospect research that used to take a person 15 minutes

Through my own agency, I built a pipeline on each client's own systems that researched every prospect and drafted a personal first line, subject and email. It connected to their CRM and data tools, and I ran the email infrastructure behind it.

15 min → 30 sec
research time per prospect
1,784
qualified meetings booked

Other things I've built

  • A campaign-setup tool for a marketing agency that cut 6 hours of setup per client down to minutes, from a single intake form.
  • An invoicing system for a construction company.
  • The CRM for my own real estate firm, built twice as we grew. It carried 100+ transactions and sent automated reports to the firm's lenders.
  • Laboratory information systems at two of the Air Force's largest hospitals, where my automation projects saved $855K.

How a pilot works

A few weeks on one workflow, measured before and after, so the decision about what comes next is based on your own numbers.

  1. 1

    Pick one job

    We choose the workflow that eats the most hours and follows clear rules. Usually it's something your team retypes.

  2. 2

    Time it as it runs today

    Before I build anything, we measure the minutes per order or invoice and how often mistakes slip through.

  3. 3

    Build it with a person approving

    The system does the work and stages it. Your team checks and approves every item while we tune it.

  4. 4

    Measure again and decide

    Same measurement, new system. If the savings are worth it, I stay on to run it and we pick the next job.

Your team stays in charge

Nothing goes to a customer or into your books without a person signing off until you decide it should.

After the pilot

What I'm looking for is a long working relationship with a small number of companies. It works like having a fractional CTO who also builds the systems: I own the technology side of the business and keep it running as it grows.

About me

I'm Dan Wilson. Building AI agents is my full-time work. I run the AI program for a large company's sales organization: I build the agents, teach people to use them, and show leadership what they return. Before that, I ran my own automation practice for two years.

I spent 14 years as a U.S. Air Force officer, leading laboratory operations across four bases with teams of up to 90 people. I also ran the lab systems at two of the Air Force's largest hospitals, moving more than 742,000 test results a year into the patient record. That's where I learned to build systems that check their own accuracy.

I'm also a small business owner. I've invested in real estate for more than 12 years and manage about two dozen rentals myself, with an AI system I built handling a lot of the office work. I know what it's like when every hour of paperwork comes out of your own week.

28
Production AI agents I built and run
14 years
U.S. Air Force officer, running lab operations
MBA
University of Washington
2 dozen
Rentals I own and manage myself
Dan Wilson

Tell me which job takes the most hours at your company.

I'll tell you whether it's a good fit for automation and what a pilot on it would look like. Every message comes straight to me, and I answer them myself.

Prefer email? dan@bedrockprocess.com