{"id":13153,"date":"2026-08-29T10:00:00","date_gmt":"2026-08-29T10:00:00","guid":{"rendered":"https:\/\/meriaky.com\/?p=13153"},"modified":"2026-08-27T00:55:29","modified_gmt":"2026-08-27T00:55:29","slug":"start-small","status":"publish","type":"post","link":"https:\/\/meriaky.com\/en\/blog\/start-small\/","title":{"rendered":"Start small: the shortest path to big"},"content":{"rendered":"\n

Start small: that’s the method that actually moves a project forward, not a big plan waiting for the perfect moment.<\/strong> The classic example: a plumber wants to redo his entire client follow-up at once, contact form, automatic reminders, invoicing, review requests. Six months later, nothing has moved.<\/p>\n\n\n\n

The plan sits in a file, never launched, because everything has to be planned to perfection first. Meanwhile, a competitor just sends a quick manual text after every missed call, and that’s already enough to land the appointment.<\/p>\n\n\n\n

The big plan that stays in a drawer<\/h2>\n\n\n\n

The big plan stays in a drawer because it never has a clear start date. It waits for the right time, the right team, the right budget. So it never exists anywhere but on paper.<\/p>\n\n\n\n

This scenario shows up constantly among service business owners. A list of twelve tasks to automate, a three page spec, and zero of it built a year later. The plan was solid on paper. It simply never started.<\/p>\n\n\n\n

Meanwhile the daily pain point keeps costing time, week after week. Every week without action is one more week of answering by hand, following up by hand, invoicing by hand.<\/p>\n\n\n\n

Why the brain prefers the big project<\/h2>\n\n\n\n

The brain prefers the big project because it feels good and carries zero risk as long as it hasn’t started. Imagining the perfect version costs nothing and can never fail. So you stay in the idea, never in the execution.<\/p>\n\n\n\n

A big plan even feels like progress, just by thinking about it. But planning to automate an entire department doesn’t save anyone a minute. Instead, the first piece that actually runs, even a rough one, produces a measurable result in the first week.<\/p>\n\n\n\n

So the real risk isn’t picking the wrong solution. It’s staying six more months in the planning phase, while the pain point keeps costing money, week after week.<\/p>\n\n\n\n

Start small: pick the right pain point<\/h2>\n\n\n\n

Start small means choosing one pain point, the most frequent one, not the most impressive one. The hardest task isn’t the one that deserves fixing first. It’s the one that comes back every day and eats the most time.<\/p>\n\n\n\n

For example, answering the same confirmation text twenty times a week costs more, over a month, than a full rebuild of the client journey. So to start small, ask yourself one question: what comes back every day that I could fix this week?<\/p>\n\n\n\n

That question wipes out half the ideas on the big plan instantly. Some tasks are rare, others are already tolerable. What’s left is the real pain point, the one you’d rather never do by hand again.<\/p>\n\n\n\n

\"First<\/figure>\n\n\n\n

Ship one simple piece that works<\/h2>\n\n\n\n

Shipping one simple piece that works always beats a complete system stuck on paper. A simple version, even a limited one, produces a result by next week. A perfect plan produces nothing until it launches.<\/p>\n\n\n\n

Take the plumber again. Instead of the full twelve-step system, one automation is enough to start: a follow-up text sent two hours after every missed call. One piece, not twelve. The result shows up within days.<\/p>\n\n\n\n

This piece isn’t perfect. It doesn’t handle edge cases or rare exceptions. But it runs, every day, without anyone touching it. And a piece that runs beats a perfect system still waiting to launch.<\/p>\n\n\n\n

Proof before you expand<\/h2>\n\n\n\n

Proof before you expand is the rule that protects the rest of the project. Each small win funds and justifies the next one. Without proof, every new step gets debated and delayed.<\/p>\n\n\n\n

A landmark study published in Harvard Business Review, led by Teresa Amabile and Steven Kramer, found that visible progress, even minor progress, is the single biggest driver of motivation at work, ahead of recognition or money (The Power of Small Wins<\/a>). In other words, one concrete small win outweighs a big promise.<\/p>\n\n\n\n

For our plumber, the proof comes down to one number: the share of missed calls called back within an hour, measured before and after the piece goes live. So when that number climbs in the first week, the next steps justify themselves: automatic booking, then a review request after every job. Without that first proof, the rest would stay in a drawer too.<\/p>\n\n\n\n

Start small doesn’t mean think small<\/h2>\n\n\n\n

Start small doesn’t mean think small: it’s the shortest path to a project that eventually becomes big. The difference sits in the order of the steps, not in the final ambition.<\/p>\n\n\n\n

The big system still exists, somewhere in the back of your mind. But it gets built one piece at a time, each one funded by the last, never in one block. We covered this logic in more detail in our article on how to automate step by step<\/a> instead of redoing everything at once.<\/p>\n\n\n\n

So aiming big is still a good idea. Getting there small, one step at a time, is simply the only way to actually get there.<\/p>\n\n\n\n

Start small this week<\/h2>\n\n\n\n

To start small this week, just put a number on your first pain point: how many hours it costs you every month. That number alone is often enough to decide what to automate first.<\/p>\n\n\n\n

Use our manual tasks cost calculator<\/a> to find out in two minutes. Then pick one piece, the simplest one you can, and launch it this week.<\/p>\n\n\n\n

Frequently asked questions<\/h2>\n\n\n\n
Why start small instead of redoing everything at once?<\/strong><\/strong>

Because a big plan always waits for the perfect moment, and that moment never comes. Start small instead: it produces a result within the first week, and that result funds what comes next.<\/p> <\/div>

How do you pick the first thing to automate when you want to start small?<\/strong><\/strong>

Pick the most frequent pain point, not the most impressive one. So the task that comes back every day weighs more over a month than a full rebuild you’ll rarely need.<\/p> <\/div>

Is a big project doomed if it doesn’t start small?<\/strong><\/strong>

Not doomed, just often doomed to wait. A project that starts with one small piece that actually runs is already moving, while the big plan is still sitting on paper.<\/p> <\/div> <\/div>\n\n\n\n