> Short answer: Running agency work as a "product" you keep building on, rather than a one-off "project", lets repeatable work accumulate and makes bottlenecks visible. But if you try to systematize everything, the process smothers the work itself. The rule is simple: build the repeatable part once, and leave the rest alone.
For years on the agency side I saw the work as a "project". A brief comes in, the team gathers, the work ships, it gets delivered, you move to the next one. It made sense; everyone worked that way. But at some point I noticed we were redoing the same things from scratch on every new project. The same folder structure, the same approval rounds, the same "which one was the final version" conversations. Work got finished, but nothing accumulated.
When I started my own venture I had to change this, because now I was wearing two hats at once: the one doing the work and the one building the system. That is when I started thinking about agency work as a product. A product is not a one-off delivery; it is something that runs again and again and that you can build on top of.
The way we made decisions changed
We used to ask "how do we do this on this project". Now we ask "if we build this once, how does it run across the next ten projects". Those two questions produce very different work. The first chases speed, the second durability. You need both, but knowing which to ask when is half the job.
Building a system is not putting everything under a rule
Let me be honest: this shift was not free. On our first attempt we tried to systematize everything and slowed to a crawl. For a simple landing page we added three approval layers, four templates, two documentation steps. When the client said "I just wanted the page", we understood the process had smothered the work.
Then the lesson landed: building a system is not putting everything under a rule. It is putting the repeatable part under a rule and leaving the rest untouched. If you are doing something a second time the same way, that is where a template belongs. Writing a template for something that happens once is more burden than solution.
Visibility arrived late but was the biggest win
When you manage the work like a product, you can see where it gets stuck. Which step is always late, whose desk a task is waiting on, which decision has not been made for three days. With an agency mindset these get waved off as "everyone is busy". With a product mindset they are bottlenecks to be cleared.
That is exactly why we built Poitim the way we did. Not to solve someone else's problem, but first to clear the clutter on our own desk: keeping a team's work, communication, and operations in one place as a system that accumulates.
A practical suggestion for small teams
Starting the next job, ask not "how do I deliver this" but "if I build it once, what remains for next time". The answer is usually one extra hour of work; but that hour saves half a day on each of the next ten jobs.
Do not systematize everything. But never do the repeatable part twice from scratch.
