When we think of ERP (Enterprise Resource Planning), the image that usually comes to mind is some massive, monolithic system designed for large-scale enterprises — dashboards everywhere, acronyms flying, integrations galore.
I used to think that way too.
Before joining a micro company nearly 10 months ago, I was already deep into ERP — reading books, exploring architectures, and studying how real businesses streamline operations through software.
As an experienced solo software engineer, I had already built projects, shipped features, and tackled real-world problems on my own.
But here’s the twist, I didn’t join the company as a software engineer since there simply wasn’t a place for that kind of role at the time. The company wasn’t thinking in terms of software yet, and building internal tools wasn’t really part of the picture.
There wasn’t a software culture in place. No dev team. No technical roadmap.
Software just hadn’t been part of the equation yet.
Still, I saw potential.
So I came in through a different door — took on another role, observed closely, stayed curious — and quietly began identifying the real pain points.
That’s when it clicked:
The theory I had studied was still valuable — but the reality on the ground was simpler.
And messier.
And far more human.
👀 From Books to Backrooms
Before stepping into a real business, most of my ERP knowledge came from research, articles, and high-level overviews:
How companies should manage resources
The importance of structured processes
Concepts like role-based access, finance modules, and best practices
But when I joined a micro company, the reality hit me:
Most small businesses run on trust, memory, and momentum.
What I found on the ground:
WhatsApp messages instead of formal sales orders
Paper notebooks in place of inventory systems
Verbal updates instead of dashboards
Problems solved informally — fast and with intuition
At first, it felt chaotic. But soon, I realized there's wisdom in simplicity, and a lot of my learning could still be applied — just with more empathy and fewer assumptions.
🛠️ My Role as a Developer
Early on, I offered to build systems that could really help — like an inventory tracker tailored for auto parts and a streamlined invoicing app.
The team appreciated the ideas, but for various reasons, they didn’t move forward with implementation.
But I didn’t get frustrated.
Instead, I used the opportunity to dive deeper into real-world business problems — and began building something reusable during my free hours.
A modular, adaptable ERP system — designed specifically for micro and small businesses.
Here’s what I’ve been working on so far:
✅ Self-attendance via browser GPS
I used the browser’s native location API to verify user presence, with basic safeguards to prevent spoofed requests.
Next steps include more advanced protections — like preventing credential misuse (e.g., one user logging in as another) and securing sessions without friction.
📦 Inventory tracking built on real-world workflows
Instead of pushing users to change how they work, I designed an inventory module around how they already track stock — minimal data entry, fast updates, and low-stock alerts.
📈 Income and expense logging without the overhead
Just enough structure to capture daily financial activity, without burdening users with accounting complexity.
(Eventually, it can plug into a larger finance module.)
🔔 A flexible notification system
Rather than relying on WhatsApp or email, I’m building a notification engine that works across multiple channels — in-app, toast, push, and potentially WhatsApp if the user prefers it.
🌍 Internationalization (i18n) ready
From day one, I’ve been building with localization in mind — supporting right-to-left languages (like Arabic), multi-currency input, and region-specific formats.
Because real-world users aren’t all in one country — or even one language.
⚡ The Spark That Led Me to Write This
Recently, I was offered an opportunity to take on a new project inside the company — something related to a property booking.
It came with a small testing phase, where I’d have the chance to design and implement a real, functional system from scratch.
That moment sparked this post.
It reminded me how much I’ve observed, learned, and quietly built over the past months — and how much of it is finally starting to connect.
This blog is a reflection of that journey — a way to document the mindset, the process, and the principles behind the software I’m building, both for this business and others like it.
🌱 Micro ERP Is Still ERP
Even if it doesn't have 100+ features...
If it helps a shop owner track who showed up, what got sold, and who still owes money — that’s ERP enough for them.
That’s the mindset I’m embracing:
Modular. Developer-friendly. Human-first. Grows as they grow.
🚀 Building Beyond the Day Job
In my free hours, I’ve been building a reusable app — inspired by what I’ve seen firsthand — to serve micro businesses like the one I work in.
It’s not about creating the next SAP.
It’s about giving real people tools that help, not overwhelm.
💬 What's Next?
I'll be sharing more soon — about specific modules like attendance, invoicing, and inventory — along with real-world feedback, code decisions, and UX lessons learned the hard (but rewarding) way.
If you're a developer curious about building practical tools for real people — not just dashboards for dashboards' sake — follow along.
We’re not just writing software.
We’re helping people breathe easier.
Top comments (0)