How I study an industry before I pitch it
Before a first meeting I learn how the industry makes and loses money, map the workflow, and build a small clickable demo around the owner's own numbers. Here's the 5-step method.
On this page
Most first calls with a business owner go the same way. They tell me what’s broken, and I ask a lot of basic questions about an industry I’ve never worked in. That’s slow for both of us, and it doesn’t build much trust.
So before a pitch, I do the homework first and bring a small clickable demo. Here is the method, step by step.
1. Learn how the industry makes and loses money
Before I look at the company, I look at its industry. How does money come in? Where does it leak?
Take an outdoor advertising agency that makes and installs its own work: billboards, shop signs, banners, light boxes. Money comes from producing and installing them for clients. It leaks through reprints after a late design change, install crews waiting for a missing approval, and invoices nobody chases once the job is up.
To learn this I read industry articles, competitor websites, reviews and job posts. Job posts are underrated: they show which roles a company has and which tools it already uses.
2. Map who does what, and where work waits
Next I sketch how one order moves from the first call to the final payment. Who touches it, which tool they use, and where it sits waiting.
For the agency that looked like this: order, design, client approval, production, installation, payment. Most problems live in the handoffs. An approval waits in a chat while production can’t start. The install crew finds out about today’s jobs in the morning. Finance doesn’t know the sign is up, so the invoice goes out late.
3. Find the numbers the owner checks every morning
Owners don’t want more features. They want quick answers to a few questions:
- How much money is still outstanding?
- Which jobs are stuck waiting for client approval?
- Where are the install crews today, and what is running late?
I pick two or three of these. They become the first screen of the demo.
4. Build a clickable demo around them
Then I build a small demo with mock data. For the agency it was one screen: orders by stage from design to installation, jobs waiting for approval, overdue invoices and today’s install schedule. I also added an AI assistant you can ask “how much money is outstanding?” and it answers from the data.
To be clear, it’s a demo, not the product. No real data, no integrations. Its only job is to show that I understood the business and that the system is buildable.
5. Walk them through their own day in it
In the meeting I don’t show slides. I open the demo and walk through a normal day in their business: a new order comes in, it moves through the stages, the owner checks the numbers in the morning.
This is where it gets good. They start correcting me: “we take a deposit before production”, “we also install LED screens”. Every correction is a requirement I didn’t have to dig for.
Why it works
- They see that I understand their business before paying anything.
- We talk about their workflow, not about technology.
- The scope gets concrete fast, so the quote is honest.
This is how I won a deal with an outdoor advertising agency, and I’ve used the same approach with a pharma distribution company to shape the design before any build.
What it’s not
It’s not free custom work. The demo is small, uses mock data and doesn’t touch the client’s systems. The real build starts only after we agree on the scope.
Want to see what this looks like for your business?
If your work moves through stages, like orders, jobs or projects, send me a short note with your industry and how a typical job runs today. I’ll reply with what I would put on the first screen, and we can decide together if a demo makes sense.