in this article
- The rule: automate the repeat, not the judgment
- Five workflows worth building
- Prompts that hold up on the tenth use
- What a week looks like after
- Guardrails for a team with no legal department
Written by Tayloe Hansen — strategy and AI innovation at For One Studios.
Automate the repeat, not the judgment.
A small team does not need an AI strategy. It needs four or five workflows that run the same way every week, so the hours go back into the work only a person can do — the ask, the relationship, the call.
The test for any workflow: does this happen at least weekly, and does it start from material we already own? Yes to both, automate the first draft. No to either, leave it alone.
five workflows
Build these in order.
01
Repurposing
One long asset in — a film, a webinar, a sermon, a keynote — and a fixed set of outputs back: transcript, three vertical cuts with captions, two emails, five social posts, one landing block. Build this first. It returns hours in week one and never stops.
02
Drafting from your own voice
Keep a single reference file of your five best emails and your brand voice rules. Every draft request starts by pointing at that file. Generic AI copy is almost always a missing-context problem, not a model problem.
03
Reporting
Export the CSV, ask plain questions of it, and have the answer written as five bullets a director can read. Replaces the monthly report nobody had time to build. Never paste identifiable records — strip names and emails first.
04
Story sourcing
Transcribe every interview and site visit, then pull the usable quotes and the follow-up questions you missed. For most teams the bottleneck is finding stories, not writing them.
05
Intake and triage
Inbound form, email, or DM gets summarized, tagged, and routed with a suggested reply a human sends. Automate the sorting, never the send.
prompting
Five habits that separate useful output from filler.
Give it the artifact, not the topic
Paste the transcript, the past email, the brief. A prompt with no source material produces the average of the internet.
Name the reader and the action
"Written for a lapsed donor who gave once in 2023; the action is one click to a giving page." Vague audience is the top cause of bad output.
Ask for options, not a final
Three subject lines, three openers, three lengths. You are buying variation to choose from, not a finished piece.
Make it show its sources
For anything factual, require the quote or line it came from. If it cannot point at the source, treat it as invented.
Save the prompt that worked
A four-line saved prompt used weekly beats a clever one-off. Keep them in one doc the whole team can open.
the week after
What a week looks like once these run.
Monday
Repurpose
Last week's asset becomes this week's calendar in about 40 minutes.
Tuesday
Draft
Every send for the week hits a 70% draft in one sitting. Humans finish the ask lines.
Thursday
Read the data
One export, five bullets, one decision. No dashboard project required.
Friday
Source stories
One interview recorded and transcribed. The pipeline is the point.
guardrails
Six lines to agree on before you start.
A small team does not need a policy document. It needs these six answered and written down where everyone can see them.
- 01
Named tools only — list what staff may use, and nothing else.
- 02
Never paste donor, client, minor, health, or contract-restricted data.
- 03
No synthetic people, voices, or testimony in anything public.
- 04
Every public number is verified by a person against the source.
- 05
One named approver for donor- or customer-facing output.
- 06
One review date each year to revisit all of the above.
questions we get asked
How many tools does a two-person team need?
One capable assistant, one transcription tool, and one automation tool to connect forms and inboxes. Everything past that tends to be a subscription nobody opens by week five.
Will people be able to tell it was AI?
If you skip the voice reference file and let it write the ask, yes. Use it for drafts, structure, and analysis, and keep the sentences that carry emotion human.
Where do teams get this wrong?
They start with the tool instead of the bottleneck. Pick the hour you lose every week, build one workflow against it, and only then add another.
who wrote this
We build these workflows inside client teams.
For One Studios runs campaigns, films, and AI workflows for nonprofits, ministries, brands, and authors. Twenty minutes and we will name the two workflows worth building first.