Every developer I know has built an internal tool that nobody uses.
Including me.
We spend weeks on a beautiful UI. Custom forms. Multi-step workflows. Role-based access. Clean design.
Then the client asks: “Can you export this to Excel?”
That’s the moment you realize what they actually needed.
Not your app. A spreadsheet with a better entry form.
Here’s the uncomfortable truth: most internal tools are just spreadsheets wearing a suit.
The data goes in. Reports come out. That’s it. That’s the whole job.
And spreadsheets have been doing that job since 1979. Excel launched in 1985. Google Sheets in 2006. Billions of people use them every day. They’re not going anywhere.
So before you open VS Code, ask yourself one question.
Does this problem require a custom application? Or does it require organized data?
Most of the time, it’s the second one.
Here’s the decision ladder I use now:
Step 1: Spreadsheet.
Google Sheets or Excel. Free, shareable, familiar. If this solves the problem, stop here.
Step 2: Notion or Airtable.
You need more structure. Relational data, views, filters. Still no code required.
Step 3: WordPress or an existing CMS.
You need user accounts, content workflows, something with more control. Still no custom app.
Step 4: Build the custom app.
Everything else failed. Now you build. Now it’s worth it.
Most projects never reach step 4. Most stay at step 1 and call it done.
The mistake isn’t that developers are bad at building. The mistake is building before understanding what’s actually needed.
A spreadsheet is not a compromise. It’s a decision.
It says: I understand the problem clearly enough to use the simplest tool that works.
That’s not lazy. That’s experienced.
Start at the bottom of the ladder. Move up only when the current step breaks.
Your users will thank you. Your future self will thank you.
And your clients? They’ll probably just ask for an Excel export anyway.
What step are you on?
#marketing4devs #webdevelopment #buildinpublic #developerlife #indiehacker
Leave a Reply