The Stack
Installed after the work is understood. Not before it.
The Stack is the software, hardware, and AI we put into a company once we have seen how the work moves and where it leaks. It is customizable to the vendors, solutions, and needs that company prefers. It is not a product, and it is not the same package twice.
Two videos follow. The first is an investigation firm. The second is any small business. Both are examples. Names and numbers are sample data.
The method
The same four moves. The Stack is the third.
Every engagement follows this order. An agency, a screening firm, and a small company in another trade get the same method. Only the third move changes shape, because the tools are chosen for that company.
01
See how the work actually moves
We sit with the operation and write the path people use. Intake to invoice, or a search to a released report. We list the software, the hardware, and any AI that is actually opened, and the tools that were bought and never used. What the handbook says is not the map.
02
Find where money or accuracy leaks
Price against real cost. Work that looks busy and loses money. A record matched on a name alone. A follow-up that never leaves the owner’s inbox. Two systems that do not meet, so the same fact is typed twice. We name the leak before we touch a tool. Automating a leak only makes it faster.
03
Install the Stack, in order
This is the Stack. A short list, ranked by what changes profit or accuracy first. Pricing and roles, if those are the leak. Then software, hardware, and AI: the vendors that company already prefers stay, and what is missing gets installed. Grok can draft, sort, and take a first pass. A person still approves what is sent, signed, or filed.
04
Leave it with the people who run it
Training on their tasks, not a tour of features. Who enters what, by when, and who reviews it, written down. The owner is not the system. When the work is in the field, the investigators we recommend are held to that same standard.
One example
An investigation firm. The same four moves.
The video shows one way those moves look in an investigation firm: leads, the case, the report, and the books, with Grok on the first pass. It is one example. The Stack is customizable to the vendors, solutions, and needs that company prefers.
Names, cases, and figures are sample data. They are not a client engagement, and they are not a result we claim for the next firm.
Built around the company
Preferred vendors, solutions, and needs.
The investigation video is a configuration, not a product we hand every client. We start from the work, then choose what stays and what gets installed.
01
The vendors they prefer
Accounting, the CRM, the case system, the hardware, and the AI can be what that company already uses. We do not pull out a tool that is doing the job.
02
One case file, not the only one
In this example the case file can be Raven, partner software from Jesse Kubik. It is optional. The firm can keep the system it has. Around it we add intake, reports, and client updates.
03
A person still decides
Grok takes the first pass: the briefing, the draft, the locate, the follow-up. Someone at the firm approves what is sent, signed, or filed.
This example
What the investigation video is walking through.
The example starts where a lot of firms start: cases on a board, a dozen tools that never meet, and admin that runs into the night. The same three jobs can be arranged around a different set of vendors.
01
Win the work
Leads, outreach, proposals, and follow-up. In the example, Grok drafts and a person approves every send.
02
Work the case
Intake, the file, a locate, the report, and the client update. The case system is the one the firm prefers.
03
Run the firm
Invoicing, collections, the books, hiring, and a short report for the owner. The owner still owns the number.
The investigation example
That video, page by page.
The problem, one configuration for an investigation firm, and how an engagement like it can start. Sample data. Figures in the example are not a client result.
How this kind of work can start
Two ways an engagement like the one in the example can start. Scope follows the company.
A blueprint
We map the firm and design the Stack: tools, workflows, and a training plan. The tools are the ones that company prefers.
Build it with them
We build it and run it with the company. Scope follows the work and the size of the team.
The same idea, any business
Not one industry. Not one product.
A shorter video: follow-up, the pipeline, the invoice, the calendar, and the post. Grok drafts. A person approves what is sent. Sales, accounting, administration, and marketing, in the tools that company already prefers.
The screens are sample illustrations. Names and numbers are not a client file.
The consulting deck
Run a bigger business with the team you have.
The short video calls it map, fix, automate. That is the same method: see the work, fix the leak, install the Stack, and leave it with the team. Illustrations, not a client system. Not one industry, and not one set of vendors.
01
Accounting
Invoicing, bookkeeping support, and expense tracking.
02
Sales
The pipeline, proposals, email, and lead follow-up.
03
Administration
Scheduling, documents, contracts, and client onboarding. Reporting and the social posts sit with these.
The four moves, on this work
01
See it
Map how the follow-up, the invoice, the calendar, and the post actually move. Same first move as every engagement.
02
Fix it
Close the rework and the gaps before anything is automated. A broken process with AI on top is still broken.
03
Install it
Add the tools and the AI on a process that already holds. A person still approves what goes out.
04
Leave it
Train the people who will open it tomorrow. The owner is not the system.
Two ways to start
Written for a small team, from a solo owner through about ten people. Scope follows the team and the work.
The Blueprint
The plan, the prompts, the questions, and the workflows. An owner who wants to build it can take it from there.
Done with you
We implement that plan with the team and train them on it. Scope scales with the team and with the functions covered. It can start with one.
Tell us what you already use. We will tell you whether a Stack built around it is a fit.