Business architecture and agentic AI for information-driven businesses
Put your team’s expertise to its best use.
Structural GrowthWorks redesigns the work that stands between your people and the value they could create. We build agentic AI inside the systems you already use, so your team can put more of its expertise into better products, stronger customer relationships, and growth.
One workstream · Two to three weeks · $12,500 fixed fee · Built in your current software
Start with one workstream that holds valuable work back.
We work for owners and leadership teams of information-driven businesses.
These businesses create value through what their people know, develop, and deliver. How the work runs determines how much of that expertise reaches its potential.
We redesign that work and build the agentic AI that supports it. The starting point can be hiring and onboarding, corporate training, high-volume operations, product and service development, or the work that brings the company to its customers.
We begin with one workstream, chosen for what improving it could make possible for the business.
The first engagement
Workflow Sprint
- One workstream
- Two to three weeks
- Built in your current software
- Before-and-after measurement
- Working agents, not recommendations
- A recorded handoff and an operating guide
A good first workstream
- Runs every week
- Touches several people or systems
- Has volume, delay, or rework you can measure
- Follows rules a person can state
- Has an owner who answers for the result
Examples: Hiring-to-onboarding handoff · Corporate training intake and delivery · High-volume intake and fulfillment · Work-product development and review · Lead-to-customer handoff
Not a fit
- A wish to "use AI" with no workstream in mind
- A one-off creative project
- A software migration, a strategy deck, or a tool to buy
- Work no one owns
- Work that needs an agent to decide without a person's approval
When the real problem is a decision no one has made, we say so.
The work filling the week can crowd out the work that matters.
A better product, a stronger customer relationship, a new source of revenue: each needs attention from people who know the business. When their week is already full, that work waits. The cost includes the improvements and opportunities the company cannot pursue.
Most companies answer with more effort, more software, or more marketing. When that fails, they buy AI and point it at the process they already have. Faster broken is still broken.
The ceiling is often architectural: the work grew around the business rather than being designed for what it needs to achieve. We redesign how the work runs, then build agents to carry the workflows that support the better design.
We measure the workstream before we touch it, and again at handover.
We begin by naming the business priority the workstream needs to support. Every Sprint then records three numbers at the start and again at handover: the hours a week the work takes, the time from first input to finished result, and the errors that reach a person or a customer. Those numbers show whether the work improved; the priority gives that improvement a purpose.
The training company, a composite we follow across this site
In this illustrative composite, we would measure hours a week, enrollment turnaround, and duplicate-record errors. The business question is what the coordinator could contribute with the capacity released: helping client managers choose the right program and supporting their success.
We redesign the work first, build the agents second, and leave every approval with a person.
Architecture tells a company where to intervene. Agentic AI tells it what has become possible at that point. Most firms practice one discipline and borrow the other: the strategists cannot build the agents, and the AI shops cannot redesign a business. We do both, in the same engagement.
- The right design. We map how the work actually runs, which is rarely how the manual says it runs, and sort every step: delete it, run it as plain code, hand it to an agent, or keep it with a person.
- The right authority. A person approves every step that touches money, customers, or contracts. The agent drafts; a person sends.
- The right handover. We teach your people the new way of working before we leave, so they can run it without us.
When one of your people approves, everything the decision needs is already in front of them.
Three questions worth asking any AI firm.
Why did an operator build an AI company?
Because the problem was never simply a lack of software.
Doug Evans has spent decades operating an information-driven business where expertise, people, customers, systems, and decisions have to work together. Structural GrowthWorks grew out of that experience.
We do not begin with “What can AI do?” We begin with “How should this business work?” Then we build the systems that make the better model possible.
Have you actually run a business like mine?
Yes. Doug joined the Institute of Reading Development as a reading teacher in 1995 and has been an owner since 2013. The Institute has served more than three million families since 1970.
He has operated at national scale: 8,000 courses a year for 105,000 students across 800 locations, a call center of more than 300 agents, and hundreds of teachers recruited and trained each year across more than 80 metro areas.
That experience matters because redesigning a business is different from automating a task inside one.
Who will actually do the work on my business?
An owner leads every engagement, from the first conversation through handover.
Doug works at the points where judgment and operating experience matter most. Agents support the building, testing, and documentation under his review.
You are not handed from a sales team to a delivery team. You are not given a strategy deck and left to implement it. The work is rebuilt inside your systems, your people are taught the new way of operating, and every consequential approval remains with a person.
The larger work comes after the Sprint.
Most companies start with one Workflow Sprint. A company where one department carries the cost starts with an Enterprise Blueprint, and an Agentic Rebuild builds the scope that is approved. Optional Care keeps what we built safe, paying, and working well after handover. The larger engagements are scoped after the Sprint or a department-level assessment.
- Workflow Sprint. The first engagement, described above.
- Enterprise Blueprint. One department read through its systems for three to four weeks, every step sorted, ending in a value model and a clear go or no-go.
- Agentic Rebuild. One department rebuilt inside your systems, usually four months.
- Care. The agents kept governed, tuned, and current after the build.
Start with the work your team needs to get to.
Tell us what valuable work your team is too busy to do, and what fills the week instead. Doug Evans reads every submission and tells you plainly whether a Sprint fits.