Sign me up

Goodwork Fractional · AI Automation Specialists

Your on-demand AI team.

An AI Automation Specialist builds the tools. A senior coach reviews the work. Behind them, a full team of AI specialists and a shared library of everything they have built.

Beta rate · August design partners USD $200 to start, then USD $500 every two weeks Ten hours a week.
Sign me up

The AI specialist

Builds the automations, tests them, documents them, and keeps them running.

The coach

Sets direction, reviews the work before it reaches you, and makes sure it is pointed at something worth doing.

Your time

As little as we can manage. A kickoff call, some screen recordings, then working demos back to you.

You don't want more AI. You want the business to run faster and leaner.

Works in the tools you already run

Everything happens inside your current stack. Nobody is asking you to move platform.

No one to manage

The coach directs and reviews the work, so the day-to-day sits with us. What we need from you is direction, not supervision.

Value shows up early

You see working results in the first cycles, not at the end of a long build.

Backed by peers, not working alone

Your AI specialist does your work, but never alone. They are one of a group of Goodwork AI specialists working across other small and mid-sized businesses, sharing what they learn as they go.

So your AI specialist brings the best practices already working for businesses like yours, not first guesses. When one AI specialist solves something, the others can apply it. You benefit from every deployment, not just your own.

"It took 187 hours to work out. It takes two or three to apply it to you."

Systems our AI specialists have built and run

Cold outbound

4-5 hrs 30-60 min

Around 3,000 emails a day prepared end to end, including the quality check.

Account management

1-2 hrs 30-45 min

A full top-of-day review of every active account, pulling six systems into one view. Daily.

Recruiting documents and agents

7 hrs 3 hrs

Job ads and hiring kits drafted, boolean searches built and tested by agents, and talent supply mapped.

Where it starts: the assessment

What gets looked at

Where you are with AI today, and whether the foundations underneath are solid or thin: how decisions get made, SOPs, data and where it lives, tools and overlap, and who owns what.

What you get back

A written picture of the current state, the gaps worth closing, and a sequenced plan with the quick wins first.

From there, you decide what to do next: keep going with the team, build it yourself, or stop.

How the work runs

The first cycle

Kickoff and access, then we map the workflows with the people who run them. The first build is agreed and underway.

Progress, shared

You see a working version and react to something real rather than a spec. Refine, or move on.

Every cycle after

Two-week cycles: build, share, decide. Documentation and a handover note travel with each build.

Quick wins come first, deliberately. Most of the work in any system is in the refinement, not the first version that runs, so we sequence the fast, high-value wins up front.

What the AI specialist can work on

A few ideas to start from, not a fixed menu.

AI hygiene and token spend

What your AI tools are actually costing, with guardrails and access locked down. Most teams have no idea.

One dashboard for the whole business

Your data centralized into a single company OS, wired to source systems rather than kept by hand.

Build versus buy

Rebuilding a SaaS tool in-house when it pays off, or an honest read on whether that is even a good idea.

Internal tools and agents

The repetitive manual work that eats the week, handed to automation.

Sales and marketing systems

Pipeline, follow-up, outbound, and a content machine that keeps producing.

Training and adoption

Sitting with your team so what gets built actually gets used. The hardest part, and the one that decides whether any of it works.

Frequently asked questions

Who manages this person?

That is why there are two people, not one. The coach directs the work and reviews it, so the management load sits with us. What we need from you is a view on what matters, not day-to-day supervision.

We already have developers. Why would we need this?

Often you don't, and the assessment will say so. Where it tends to help is the part a dev team structurally can't do: sitting with people so they actually adopt what has been built, and the operational workflows that never reach the top of a dev queue.

What if we stop?

Everything built is yours, along with the documentation. If you stop, you keep it and you can run it.

What about access to our systems?

Named accounts you create and can revoke, at the lowest permission the work needs. No shared logins. NDA and confidentiality terms as standard.

What will the tools cost on top?

For most automation work, roughly $30 to $100 a month. You see the estimate before anything gets built.

What if we don't know what to automate?

That is what the assessment is for. Most people don't.

When does it stop being the right fit?

If the work runs past roughly twenty hours a week, or you already have people building this full time, a fractional seat is the wrong shape. We will say so, and we can help you hire a dedicated resource and hand the work over cleanly.

What is a design partner?

You get the August beta rate and you shape what gets built. In return we ask for candid feedback at the end of each cycle.

USD $200

assessment to start

You get the plan and sequence, then decide whether to proceed.

USD $500

every two weeks

Ten hours a week, no commitment, stop whenever it stops earning its keep.

Sign me up

Beta rate for August design partners.