bVan! SystemsPractical Intelligence. Better Systems.

Bring me the problem.

We make the business work better.

The workaround everyone knows about. The handoff that keeps dropping things. The information typed in three places, and the process that only works when one person is in. I’m Billy. I find what’s actually wrong — and build the practical fix.

Bring me the problem See the work

How it runs todayNew customer inquiry

Concept: one everyday workflow, before and after.

Act I: The problem

Most small businesses aren’t broken. They’re held together by workarounds.

Disconnected tools, repetitive admin, information stuck in one person’s head, and systems that create more work than they save. None of it is dramatic. All of it costs time, every day.

What’s harder than it should be?
The job that takes twice as long as it ought to, every single time.
What keeps breaking?
The handoff that stalls, the detail that gets dropped, the fix that never sticks.
What are you still doing by hand?
Retyping, re-sending and re-checking the same information because nobody has fixed it.
What only works because one person knows how?
The process that lives in someone’s head and stops when they’re out.
Which tools don’t talk to each other?
The software you pay for that still needs a person in the middle copying things across.
What have you been meaning to fix for months?
The thing that keeps sliding to next week because the day job comes first.

A desk buried under stacks of paperwork and sticky notes. — Everything is somewhere. Finding it is the job.

The same kind of desk, cleared: one folder, a notebook and two pens laid out in order. — Everything has a place, an owner and a next step.

The useful question isn’t “which software should I buy?” It’s “what is actually causing this?”

You don’t need a diagnosis, the right terminology or a plan before you reach out. Working that out is my job.

Act II: The problem solver

Tools change. Industries change. The discipline doesn’t.

bVan! is founder-led on purpose. When you bring a problem here, you’re working with me — the person who asks the questions, finds the fault and builds the fix.

Billy, founder of bVan!, smiling in a purple shirt and dark tie against a red backdrop. — BillyFounder, bVan!

“I’ve always been a tinkerer — the guy who wants to understand how things work. I look for patterns, bottlenecks, pinch points, and the real cause behind a problem.”

U.S. Army
Black Hawk maintenance & crew chief
An aircraft is hundreds of systems that all have to work together, every flight. You follow the procedure, trust the inspection, and never guess about a fault.
Complex systems fail at the connections.
Emissions testing
Diagnostics & technical training
Testing vehicles against a standard, and teaching other people to do the same work correctly. A fix only one person understands isn’t finished.
If you can’t explain it, it isn’t done.
Pool industry
Troubleshooting, repair & technical operations
Plumbing, electrical, automation and diagnostics — usually with a customer beside you who just wants it working again.
Start with what the person needs, not the part you’d like to replace.
Today
AI implementation, automation & systems
When my work moved away from the field, I found AI and approached it the way I approach everything: tinker with it, take it apart, learn its limits, and make it useful.
New tools. Same process.

The process that carried across

Find the problem. Understand the system. Make it work better.

You talk to me
No account managers or hand-offs. The person diagnosing is the person building.
Plain language
You’ll understand what’s wrong, what I recommend, and why.
A straight answer
If I’m not the right help for the problem, I’ll say so.

Act III: The work

Show the work. Don’t just make the claim.

Real systems, labeled for exactly what they are. Each one shows the problem, the approach, what got built — and where the same thinking fits in a business like yours. Try them: they’re live.

How to read the labels

Working prototype
A complete, runnable build with public source code and published test results.
Internal bVan! system
A system bVan! built and runs for its own operations.

Working prototypeIlsa — workflow assessment prototype

Finding where a process actually breaks

The problem: Owners usually know something is going wrong — “we keep losing new inquiries” — without knowing where. Jumping straight to new software skips the part that matters: who owns each step, and how work gets handed over.
The approach: Ask one useful question at a time. Map how the work really moves. Flag a problem only where the owner’s own words support it, keep facts, guesses and unknowns separate, and let the owner correct anything.
What got built: A working prototype that interviews, maps the workflow, traces every finding to a direct quote, and refuses to recommend anything until the process is understood. AI only proposes; ordinary code decides.
For your business: The same discipline drives the Workflow Assessment: a clear map of one workflow, the real bottleneck, and the simplest fix — before money goes into the wrong one.

Evidence

108 automated tests; runs fully without any AI service
20 pre-registered evaluation cases — 0 premature assessments across 40 runs
Public source code and evaluation results

Source & evaluation (opens GitHub in a new tab)

Workflow map · new customer inquiry

S1Customer fills out the web form
How it arrives · Automatic
S2Maria copies the details into the job spreadsheet
How it arrives · “Maria checks the inbox when she has time.”
S3Owner decides which technician handles it
How it arrives · “Maria tells the owner at the end of the day.”
S4Technician calls to set up a visit
How it arrives · “The owner texts the technician the customer name.”
S5Someone sends the quote
How it arrives · “I don’t know how that gets passed along.”

Findings — select one

Evidence

“The owner texts the technician the customer name.”

Ilsa can be wrong. The owner can correct anything, and findings update.

Recreated from the prototype’s built-in sample — a fictional plumbing company. Quotes are the sample owner’s own answers.

Working prototypeSituation Model — operations coordination prototype

Keeping urgent work moving — without letting anything act on its own

The problem: Knowing something should happen isn’t permission to make it happen. An urgent refund still needs a person’s sign-off. And when a system loses track of what it already did, a customer gets refunded twice.
The approach: Sort every incoming item into NOW, NEXT, WAITING, DECISIONS or WATCHING — the same model bVan! uses to run its own operations. Give each item an owner and an authority level, and let fixed rules, not AI, decide what may run.
What got built: A working system that blocks gated actions until a named person approves that one item, carries the action out, catches a crash mid-way, reconciles its records against the outside system, and refuses to do anything twice.
For your business: Approval steps for refunds, discounts, purchase orders or schedule changes. One shared view of what’s urgent, what’s waiting, and what needs a decision — so fewer things fall through the cracks.

Evidence

3 stress runs × 1,000 items with injected failures: 0 unauthorized or duplicate actions
The same workloads through a naive executor: 533–571 failed items per run
52 automated tests; public source code

Source & evaluation (opens GitHub in a new tab)

Operations board · order 4417

“Customer was charged twice for order 4417 and wants a refund.”

Authority: Approval required
Approval: pending
Our record: open
Payment system: —

Step 1 of 6 · Classify the requestUrgent, so it goes in NOW. Action: issue refund. Authority: approval required.

Step-through of the public Situation Model demo. The real app runs these controls in code against a simulated payment service.

Internal bVan! systemPublishing Engine

Getting finished work out the door — checked twice

The problem: Making something is only half the job. Work stalls between “done” and “live”, quality checks get skipped on busy weeks, and nobody confirms the thing actually went out.
The approach: Break production into clear stages. Give quality control to a separate check the producer can’t wave through, put a human approval in front of anything public, and verify the result once it’s live.
What got built: A multi-stage pipeline that coordinates choosing what to make, producing it, independent quality control, publication, live verification, and the handoff to marketing.
For your business: Any repeatable output — quotes, proposals, reports, listings, newsletters — moving through defined stages, with a real check before it reaches a customer.

Evidence

Used to produce and publish the Pool Owner’s Field Guide products
Quality control kept separate from production
Human approval before anything is published

Production pipeline · one work item

01ChoosePick what to make, and why
02ProduceBuild the piece
03Quality checkSeparate reviewer, own checklist
04ApproveA person signs off
05PublishRelease it
06Verify liveConfirm it actually went out
07Hand offPass to marketing

Send in a flaw

Production never grades its own work. The quality check can send it back.

Concept view of the Publishing Engine’s real stage order. Timing and the work item are illustrative.

Internal bVan! systemThe bVan! operating system

Running a one-person company like a coordinated team

The problem: A founder carries everything — sales, delivery, marketing, follow-up, decisions. The work isn’t hard to do. It’s hard to keep track of without dropping something.
The approach: Give each recurring job a defined role, a written standard, and a clear limit on what it may do alone. Send anything consequential to a single approval queue, and keep the owner as the final authority.
What got built: A governed set of AI-assisted workflows for research, marketing production, review and approval, records and retrieval — each with a versioned operating standard and a daily approval queue.
For your business: For owner-dependent businesses: routine work drafted, organized and checked by a system, while the decisions that carry consequences still come to you.

Evidence

Versioned written standards for every role
Public-facing work passes a recorded review before release
Pricing, commitments and exceptions stay with the owner

Daily queue · today’s items

Weekday social post, draftedUnsorted
Background research on a prospectUnsorted
Change to a published priceUnsorted
A client asks to add scopeUnsorted

Each item is routed by what it could affect.

Concept view. The routing rule is how bVan! runs; the items are examples.

Act IV: Working together

One practical step at a time. You decide if there’s a next one.

Bring a messy, ordinary problem — that’s exactly what this is for. It doesn’t need to be a transformation. Every stage stands on its own, and the first conversation is free.

$750 fixed
Workflow Assessment
One workflow, one clear problem. I map how the work actually moves, find the real bottleneck, check what your current tools can already do, and recommend the simplest fix.
You get a concise, decision-ready plan. Act on it yourself, with someone else, or with me.
Scoped to the need
Implementation
Building the fix — a process change, better use of tools you already pay for, automation, AI, or a mix. Tested on real cases before you rely on it.
You approve the approach before anything is built, and sign off before it goes live.
Scoped with the work
Training & Documentation
The people who use it understand it: plain-language guides, walkthroughs and a proper handover, so the system doesn’t depend on me.
Your team owns how it works.
Optional
Ongoing Optimization & Support
Checking that it’s actually helping, adjusting what isn’t, and keeping it working as the business changes.
Only if it’s useful to you.

Where most work starts

Workflow Assessment

$750fixed

One workflow. One clear problem. A practical plan for making it work better.

Your time: About 60–90 minutes for intake and interview
Turnaround: 3–5 business days after the required information is received
Scope: One defined problem within one workflow
Credit: The $750 assessment may be credited toward an implementation of $3,000 or more when approved within 30 days.

Bring me the problem

What you receive

A clear problem statement
A map of the workflow as it really runs
The most important bottlenecks and root causes
A check of what your current tools can already do
Options compared — process, people, software, automation, AI
A prioritized recommendation
Risk and human-control notes
Practical next steps

Concise and decision-ready — not a bloated consulting deck. Implementation, configuration, training and ongoing support are scoped separately — the assessment never quietly turns into them.

Separate service · AI education

AI Starter Session

Not part of the workflow path above — for owners who want to learn to use AI themselves.

$299fixed pilot

Get AI Working for Your Business.

A working session for owners who want a real, useful starting point with AI instead of a demo.

Format: Approximately 90 minutes
Who attends: Normally the owner, or the owner plus one key staff member
Requirements: No technical background required
Tooling: Can be delivered using free or basic ChatGPT

You leave with

A Business Master Prompt
A reusable AI business role/assistant for one real task
Your Next 3 AI Opportunities

How every engagement runs

Practical
The problem picks the tool. If the best fix is a process change, that’s the recommendation.
Controlled
People stay responsible for consequential decisions. Systems are tested before your business depends on them.
Measurable
We agree up front what “better” looks like, so you can see whether it’s working.

Data & confidentiality

Your business. Your information. Your call.

Fixing a workflow means seeing how your business really runs. Here’s how access, approvals, AI tools and sensitive information are handled.

I ask only for what the work needs
The forms, screenshots, examples or system views that relate to the one workflow we’re looking at — not the keys to everything.
You approve anything consequential
Nothing that changes how your business operates, spends money or talks to customers goes live without your sign-off.
AI drafts and sorts. People decide.
In the systems I build, AI can propose, summarize or classify. Fixed rules and a responsible person decide what actually happens.
Your information doesn’t go into an AI tool by default
Before any of it does, we talk about which tool, exactly what goes in, and whether it should at all.
Your work stays yours
Client work only appears on this site, or anywhere else, with your permission.
Terms in writing
Confidentiality, access, data retention and ownership of custom work are set out in the engagement agreement, not left to assumption.

What I won’t do

Promise savings or results the work hasn’t shown
Recommend AI where a simpler fix will do
Quietly expand the scope or the bill
Leave you with a system nobody on your team understands

Recommendations are based on the information available during the work and are not legal, accounting, regulatory, cybersecurity or compliance advice. How this website handles what you send it is covered in the privacy notice.

Sister studio

Sometimes the problem is how it’s explained.

bVan! Systems

Diagnosis, technical implementation, operational improvement and systems development — when the work itself is the problem.

Raven Six Creative

Brand identity, website design, social media marketing, and creative advertising.

Visit Raven Six Creative

You don’t have to sort it first. Bring the problem here and it goes where it fits — some need both.

Act V: The invitation