Automated outbound outreach case study for video production
vitapictura.co logovitapictura.coVideo production

How We Built a Sales Machine for vitapictura.co Without Hiring a Sales Rep

  • b2b
  • outbound
  • sales
11 min read

TL;DR

Vita Pictura sells production work to creative agencies. Growth in a new geography was real, but hiring a full outbound role was not. The old motion leaned on offline relationships and founder time, which is a fine base and a thin strategy if you want a second channel. The system we built does not automate charisma. It automates the grind before the conversation starts. Research, mapping services to what a company actually does, and a first-draft email. When someone replies, a human steps in for the part that should stay human.

Automation helps us operate faster within a small team. They cover a huge scope of our sales processes.

Georgius Misjura portrait

Georgius Misjura

CEO · Vita Pictura Productions

The Problem

New geography, same constraint. The work is good, the offer is clear, but pipeline cannot depend on bumping into the right people at the right events forever.

Outbound fails quietly when it is treated as a weekend task. Researching an agency, understanding what they ship, mapping that to your services, and writing a coherent cold email is not hard once. It is hard at volume, which is why it becomes intermittent.

Hiring a dedicated sales role is a real fix, but it is also a fixed cost. For a small production company, the question is whether you can buy consistency before you buy a seat.

Story: network gravity and occasional bursts

Leads showed up through relationships, referrals, and founder hustle. That can produce great clients. It does not produce a steady second channel you can tune.

  • Collect possible targets from scattered sources when energy is high.
  • Research each account manually, then lose steam before the list is exhausted.
  • Write emails from scratch each time, which makes even strong writers avoid the inbox.
  • Pause outbound for weeks because the prep work is heavier than the send button.

Reframing

The leverage is not email as a medium. The leverage is the decision stack before send. Who is worth talking to, what do they actually do, which part of your catalog maps to that reality, and what is a fair opening line given those facts.

Automating only the blast is how you get a deliverability problem and a reputation problem at the same time. The design goal here was to make the machine do homework, then let humans do persuasion.

Stability matters for memory. Spreadsheets are tempting until access, history, and operational habits wobble. A self-hosted database on Hetzner is boring infrastructure, which is the point.

Solution architecture

The pipeline starts with a lead list the founder is willing to stand behind. Garbage in still garbage out. The difference is that once a lead is admitted, the system does the deep pass on public context.

The agent returns structured research, then compares that context to a service document that describes what Vita Pictura actually sells. Matching is where a lot of "personalization" normally lies. Here it is explicit.

A draft email is generated from that match, then the workflow handles send mechanics. After that, the human work is replies, discovery, and negotiation. That is the correct handoff if you care about trust.

Lead records and context live in NocoDB, hosted on Hetzner, so the operation has a backbone that behaves like a system instead of a shared file that everyone is afraid to touch.

  1. Curate the lead list

    Admit targets with intent. The pipeline amplifies discipline or sloppiness.

  2. Run research and extraction

    Pull account context into structured fields the matcher can read.

  3. Match services to reality

    Map findings to the service catalog before wording exists.

  4. Draft, send, then get out of the way

    Generate and send the first touch, then route replies to humans.

Workflow schema

Before / After

Metric
Before
After
Channel shape
Mostly offline and opportunistic
A second, systematized outbound stream alongside the network
Where time went
Heavy prep, inconsistent follow-through
Prep automated, human time shifts to conversations
Operational memory
Fragile ad-hoc notes
Structured storage in NocoDB
Risk focus
Skipping research to save time
Research as default, with humans on quality gates where it matters

Impact

Outbound stopped being a mood and became a pipeline. That is a boring sentence that means a lot operationally.

Founder attention moved toward qualified replies instead of burning evenings on manual dossiers.

Having a stable database changes behavior. You review history, you avoid re-learning the same account, you treat outreach like something the company runs.

The honest limits stay. This writeup does not invent conversion metrics. The design goal was a believable system for a small team, not a slide deck promise.

Transferability

Strong fit for lean service businesses that sell expertise with real customization, where message quality depends on account context.

Weak fit when positioning is vague. A matcher is only as good as the catalog it reads.

Also weak if nobody will curate lead quality. Automation will happily work a bad list.

FAQ

No. The architecture assumes research and service fit happen before wording. Without that, you are just accelerating junk.
Portrait of Lev Kovalenko
Lev Kovalenko
AI consultant

I help video and sales teams find the line where automation removes drag without flattening the work that wins deals.

Special thanks

Gosha Knyazhev
AI Native Designer
gosha.ee

Read Also