Greenfield implementation, for a business without a system yet
A business that exists, but runs on the founder's memory and direct coordination between team members. No CRM, no Monday, no central spreadsheet. It works — up to a certain size. The question is to recognize when you've crossed it, and not to build a monster the day after.
If you already have tools (Monday, Trello, spreadsheets) that the work flows through — migrating to Zoho fits better. This page is about the case where there's no system yet at all.
What a business that hit the ceiling looks like
These are the signs that recur in almost every company that comes to me without an existing system:
- Leads slip through the cracksAn inquiry arrived on someone's phone while they were on vacation, and nobody knew it existed.
- You can't say how many quotes are open"How much money is on the table this month" takes half an hour of digging through files.
- No one follows up on who hasn't come backA quote sent three weeks ago is simply forgotten. It's the most expensive hole in a small business.
- Knowledge lives in one person's headIf they're sick, nobody knows what was agreed with a customer.
- Accounting and sales don't talkInvoices are issued manually, with no link between what was sold and what was billed.
Examples from the field
Renovation company, 8 employees
Leads from Facebook and referrals. Quotes in Word, follow-up in WhatsApp. The real problem wasn't organization but speed — a customer who received a quote in two days instead of a week closed at a much higher rate.
Small B2B importer
Three salespeople, a catalog of hundreds of items, different pricing per customer. Here the first system is mostly pricing and inventory, with the CRM piece secondary.
Auto shop
Appointments in a paper diary, service reminders in someone's head. A first system that does only two things — scheduling and automatic reminders — changes the calendar entirely.
Design studio
Hourly projects, billing in stages. The pain isn't sales but tracking what's been billed and what hasn't.
The principle: deliberately narrow
The most common mistake in a greenfield implementation is building the system that will fit the business in five years. That's exactly what produces the systems that end up on my desk two years later.
The first system should do three things and no more: capture every inquiry into one place, show what's open and who hasn't come back, and produce a quote in a click. Everything else waits until it's clear you actually need it.
The reason isn't only budget. A small system everyone uses beats a full system half the team routes around — and that's exactly where most implementations fail.
Choosing a system
I work mainly with Zoho, and I say that up front so you know where I'm coming from. But not every business needs Zoho, and some cases genuinely fit another platform better. If you're comparing options, I can talk about where each one wins and where each one struggles.
What the process includes
Short scoping — one to two days of understanding the process as it exists. Not how it's supposed to work, how it actually works.
Setup — building the narrow system, including the Israel-specific adaptations you need from day one.
Training — with your team, on your data, not on a demo.
Support — the first two months are what decides whether the system takes root or gets abandoned.
Not sure which path fits you?
Tell me what's happening in your business today, and I'll say whether a first system makes sense.