← All articles Operations · Case Study

How a one-person company runs its marketing engine on AI operations

Hard2Simple is one person. There is no marketing department, no content team, no agency retainer. What there is: an operating system — AI assistants for thinking, n8n for repeatable machinery, and a small set of workflows that turn raw material into finished marketing output every week. Here is the stack, what it takes, and what it replaced.

Hard2Simple company blog Case study: Lawnsy, our flagship product October 2026
1
person on the marketing team — the whole company, in fact
4
core n8n automation workflows in the marketing stack
2
lanes: AI assistants for thinking, n8n for machinery
1080×1920
vertical Shorts rendered automatically from stream transcripts
The premise

Marketing is an operations problem, not a talent problem

Most one-person companies don't have a marketing problem — they have a consistency problem. You know what to do: post regularly, repurpose content, research your market, stay visible. Then the actual work of the business eats the week, and the content calendar goes quiet for a month.

The fix most people reach for is hiring: a freelancer, a part-timer, an agency. That's a real option, but it trades one bottleneck for another — now you're managing a person instead of doing the work. We took a different route: we automated the repeatable parts and kept the judgment calls human. The result is a marketing engine that runs whether the week is busy or not, operated by one person.

Lawnsy — the lawn-care booking app we're launching in Metro Detroit, designed and built by Hard2Simple — is the running example in this piece, because it's where the engine does its daily work. But the engine isn't specific to Lawnsy. It's a pattern any lean team can copy.

The stack

Four workflows, one division of labor

The whole system rests on a single rule: AI assistants think; n8n does. Assistants like Muse handle research, drafting, editing, and strategy — the work where judgment matters. n8n handles everything repeatable — fetching, moving, converting, scheduling. Nothing is "AI magic." It's plumbing: source material goes in one end, finished output comes out the other, and a human reviews what comes out.

Workflow 1 — Video → Article

Long-form video becomes a publishable written piece without re-writing from scratch.

Source
YouTube video
A full-length video on a topic the audience cares about.
→
Automation
n8n + tubestacker.app
The workflow pulls the video, extracts the content, and drafts it into article form.
→
Output
Substack article
A draft ready for human edit and publish — the structure survives, the voice gets checked.

Workflow 2 — Clip harvesting

Raw short-form material is collected on autopilot instead of hunted down manually.

Source
playdb.app
Video clips worth repurposing, identified during normal browsing and research.
→
Automation
n8n download workflow
Clips are fetched and filed automatically — no manual downloading, renaming, or organizing.
→
Output
Clip library
A standing library of source material, ready whenever a post or edit needs it.

Workflow 3 — Market research

The product strategy feeds on research the engine gathers continuously.

Source
Web sources & signals
Industry material, competitor moves, customer conversations — whatever the research question needs.
→
Automation
n8n research workflow
Structured collection and synthesis runs for the Lawnsy app — repeatable, documented, re-runnable.
→
Output
Product insight
Findings that feed positioning, content angles, and roadmap decisions — not just content for content's sake.

Workflow 4 — Social & marketing automations

Distribution is a system, not a mood.

Source
Finished content
Articles, clips, announcements — anything the brand needs to put in front of people.
→
Automation
n8n marketing workflows
Scheduling, cross-posting, and repetitive distribution tasks run without manual babysitting.
→
Output
Consistent presence
The brand stays visible on schedule — the part one-person companies usually drop first.
The production line

From livestream to vertical Short, hands-off

The heaviest piece of machinery in the stack is the stream-clip pipeline. Livestreams produce hours of footage; short-form platforms reward sixty-second vertical cuts. Bridging that gap used to mean scrubbing through recordings by hand. Now it's a line:

The clip line

Raw footage in, captioned vertical video out.

Source
Stream recording
A full livestream — the raw material.
→
Transcribe
faster-whisper
Local speech-to-text turns the audio into a timestamped transcript — the map of everything said.
→
Render
ffmpeg
Selected segments are cut and rendered as 1080×1920 vertical video with burned-in captions.
→
Output
Shorts, ready to post
Finished vertical clips — hook, captions, format — awaiting a final human review before publishing.

The key word is pipeline, not autopilot. The transcript tells you where the good moments are; the render makes them postable. But a human still picks the moments and still approves the cut. The machine does the tedious middle — scrubbing, timing captions, re-encoding — so the human hour goes to taste, not toil.

The rule that makes it work

Thinking and machinery stay in their lanes

Every failed "AI marketing" story we've seen fails the same way: someone asks the machine to do the thinking. The output is generic, the voice is off, and the audience can smell it. Our rule is strict — and it's the whole reason the engine works:

Lane 1 — Thinking

AI assistants (like Muse)

  • Research: dig through sources, summarize, compare
  • Drafting: first versions of articles, scripts, posts
  • Editing: tighten, restructure, check consistency
  • Strategy: weigh angles, plan calendars, pressure-test ideas
Lane 2 — Machinery

n8n workflows

  • Fetching: pull videos, clips, and source material
  • Converting: video → transcript → article draft → formatted output
  • Moving: file, name, organize, and route assets
  • Scheduling: run distribution on time, every time
AI doesn't replace the marketer. It replaces the marketing department's busywork — so one marketer can do the department's work.
Before & after

What the engine replaced

Nothing here is theoretical. Every workflow in the stack exists because the manual version was either not getting done or eating hours it shouldn't. Side by side:

The manual way

  • Repurposing a video meant re-watching it and re-writing it from a blank page
  • Clip ideas lived in bookmarks and memory — most were never downloaded, let alone used
  • Market research happened in bursts before big decisions, then went stale
  • Posting cadence depended on how the week went — busy weeks meant silence
  • Cutting a Short meant scrubbing hours of footage and hand-timing captions

The engine way

  • Video → article draft arrives as structured raw material; the human edits, doesn't originate
  • Clips are fetched and filed automatically into a standing library
  • Research workflows re-run on demand — findings stay current by default
  • Distribution runs on schedule regardless of how the week went
  • Transcription maps the footage; ffmpeg renders the cut — the human picks moments and approves
The honest accounting

What it takes — and what it doesn't

Let's be direct about the ledger, because "AI does your marketing" usually hides the real price tag. Here's ours:

What it took

  • Time to design and wire each workflow — real hours, up front
  • Learning the tools well enough to trust them: n8n, transcription, ffmpeg
  • Ongoing attention: reviewing output, fixing what breaks, improving prompts

What it didn't take

  • No marketing hire, no freelancer management overhead
  • No agency retainer, no per-post production fees
  • No enterprise platform — the stack is commodity tooling, wired together

What it replaced

  • The choice between doing marketing badly and not doing it at all
  • Hours of scrubbing, downloading, transcribing, and reformatting by hand
  • The inconsistency tax — going quiet exactly when visibility matters most

Honesty gate: what the engine doesn't do

The takeaway

This is a capability, not an experiment

The point of this piece isn't that the tools are cool — it's that AI content operations is now a real capability for lean teams. A one-person company can run a marketing function that used to require a team: research, repurposing, distribution, and short-form production, all operating on schedule, all under one person's judgment.

The pattern transfers. Swap Lawnsy for any small business with expertise worth sharing and a founder without spare hours, and the same engine applies: assistants for thinking, automation for machinery, a human in the loop at every point where taste matters.

That's what Hard2Simple does — put AI to work on real operations, for real one-person companies. Lawnsy is our proof of concept. Your business could be next.

Want an engine like this running your business?

Hard2Simple helps lean teams and solo founders put AI to work — from content operations like this one to custom websites and apps. If you're doing the work of three people, let's talk about which parts the machine should take.