Before You Pay Anyone to Build You Something: Three Questions
A client came to us with a problem most owners will recognize. They had five or more email accounts, and they wanted one place to watch them all. They also wanted email that turned into a task, so things stopped getting lost between the inbox and the to-do list.
The goal was right. Every first idea for reaching it was a build.
The three builds that felt helpful
There were three obvious ways to do it:
- A new mailbox that everything forwards into.
- A forwarding-and-filters contraption wired across all the accounts.
- A Zapier or Make automation to turn emails into tasks.
Each one felt generous to offer. Each one was wrong, for the same reason: every new mailbox, alias, automation or script is something someone has to secure, monitor and maintain. Any of them can also fail without telling anyone. The new mailbox had a more immediate problem too: it breaks replies.
Building someone a thing quietly makes you the owner of that thing forever. That’s a bad trade for both of you if a tool they already pay for could have done the job.
Question 1: Does an existing tool already do this?
Usually, yes. In this case, three tools the client already had covered it: Gmail’s forwarding, Gmail’s “send mail as,” and Notion’s built-in email-in address. They’re battle-tested and maintained by someone else, and nobody has to support them. Reach for those first.
Question 2: Can you configure it yourself?
Forwarding rules, send-as and filters are settings. Settings you own are durable, and they don’t turn anyone into your sysadmin. The useful thing someone can do here is describe the steps clearly. You click.
Question 3: Would the build make someone the silent point of failure?
This is the one owners skip. An automation that should have created a task, and didn’t, is worse than having no system, because you trust it. If a failure would be invisible and the stakes are high, nobody should freehand it.
What we handed over instead
A setup guide, not a system. Five things the client switched on themselves:
- Gmail forwarding
- “Send mail as”
- Reply from the same address the mail came to
- Filters
- Notion’s existing email-in address
We built nothing and have nothing to maintain. The richer, automated version wasn’t refused. It was deferred to a scoped, paid later phase, which is when a build earns its upkeep.
The three answers to “can you build me…?”
| When | The move | What you’re left with |
|---|---|---|
| An existing tool fits, and you can configure it | Recommend | A clear guide. You own the config. |
| Automation is genuinely wanted, and the value clears the cost of maintaining it | Scope it as a paid build: a change order or a later phase | A build that’s priced to be maintained |
| It just feels helpful in the moment | Never | A permanent liability bought to solve a temporary itch |
One of these leaves you with an asset. The others, done carelessly, leave you with a chore.
Where the Sprint starts
If you’re past the basics (your listings are fixed and you’re spending real money on marketing), this is the order we work in. The 14-Day Growth Sprint opens with a full stack audit: “Every tool, listing, account, and customer list — mapped and checked before a dollar goes to growth.” Then we connect what you have before adding anything new.
It’s $2,000 flat, and it starts with a free scoping call: ziplinecreative.io/sprint
Want this done for your business?
Marketing operations for small business usually doesn't need another tool. Three questions to ask before anyone builds you a new system, and what we handed a client instead.