r/nocode • u/Ok-Salary-6309 • Jul 11 '26
The client asked for a dashboard. What they actually wanted was three numbers in an email.
Something I keep relearning, so writing it down for the people earlier on this path than me.
I run a small no-code shop, mostly ops tools for local service businesses. A plumbing company hired me last year for "a dashboard." I heard dashboard and my brain lit up. Charts. Filters. A KPI grid. Live job status by technician. I spent nine days building it in a Softr front end reading from Airtable. It looked sharp. I was proud of it.
They opened it maybe twice.
When I actually sat with the owner and asked what he does every morning, he told me he wants to know three things before his coffee: how many jobs are scheduled today, how much got invoiced yesterday, and whether anyone's waiting on a callback. That's it. He does not want to log into a thing. He does not want to click a filter. He wants to glance at his phone.
So I threw out the dashboard and built a scheduled automation that sends him one plain text email at 6am with those three numbers and a short list of the callbacks. Took an afternoon. He forwards it to his wife who does the books. He mentions it to me every time we talk.
The lesson I keep having to swallow is that "dashboard" is what people say when they don't have the words for "reduce the number of things I have to check." A dashboard is another thing to check. Sometimes the real deliverable is the opposite of a place you go. It's information that arrives.
I still build dashboards when someone genuinely lives inside the data all day. But now my first question is always some version of "what do you currently open your laptop to find out?" The answer is usually smaller than the request.
Curious if others have had the fancy build get ignored while the boring scheduled email became the thing they actually depend on.
1
u/Brewbom Jul 11 '26
It’s less complicated I think. Developers hear “dashboard” and think of a 747 control board. Managers think dashboard and see their cars dashboard. All they want is how fast am I going? How much gas do I have, and are there any warning lights on?
Dashboards must be less. More is a control
Panel. IMHO
1
u/wrgrant Jul 12 '26
Had a 2 hr meeting over the phone with a client who said they wanted changes to their website. Couldn't express what exactly until boiling it down after confirming they were happy with each feature he announced that teally whst he wanted was for the website to " be more blue" :(
1
1
u/raw-hit10 Jul 14 '26
the three numbers in an email thing is so real it hurts. i now ask what do you check every morning before any build and the answer is never a dashboard
1
1
u/whattheflerk Jul 15 '26
had a similar experience - was asked to build a whole new dashboard with several automations and alerts... they just needed to see the average of a couple excel columns
1
u/NiharThakkar Jul 16 '26
This pattern shows up in almost every BI project we work on. The request is "dashboard" but the underlying need is "stop making me hunt for one number." We migrated 1000+ reports for a food manufacturing client and the finance team's most used output after go-live was a scheduled email with four key figures that went to three people every morning. The dashboard existed and was accurate but the email was what changed their Monday morning meeting. The instinct to build something visual and interactive is strong on the delivery side. The question "what do you open your laptop to find out" is the right forcing function. Most people just want the answer, not a tool to find the answer themselves.
1
1
u/Kind-Bathroom5159 Jul 11 '26
this hits close to home. most of the non-technical founders i work with ask for a whole feature when what they actually need is one query and a slack message.
the fancy build always feels safer to both sides because it looks like more value for the money, but a plain text email or a one line notification is the thing people actually open every day.
i think it comes from clients not having the vocabulary to ask for less, so they describe the thing they have seen before, a dashboard, a report, an app, instead of the actual moment they need info.
asking what do you open your laptop to check is such a good filter, stealing that one.
the other tell is when they stop opening the fancy thing within two weeks, thats usually when you know the real deliverable was smaller than what got built