Back in 2017, I was running a small e-commerce store out of my kitchen. Nothing fancy—just me, a laptop, and the constant hum of the refrigerator. Orders came in, I packaged boxes, and shipped them out. But every week, I’d be overwhelmed by how much time I spent chasing payment statuses, checking shipping labels, and manually entering data into multiple systems. I started keeping track of it all on a spreadsheet.
What began as a simple tracking tool became a messy web of tabs—sales by day, customer notes, tax breakdowns, shipping logs. I’d spend Friday evenings trying to reconcile numbers that never quite matched. One rainy Tuesday, I opened the file looking for something specific and saw it: a row that said “$0.00 at 2:14 PM” with no order number attached. It wasn’t an error. It was money lost—unrecorded, unclaimed. That moment made me realize I couldn’t keep doing this manually.
I tried off-the-shelf tools first—some claimed to automate everything—but they were either too complex or too generic. I didn’t want to bend my workflow to fit software. What I needed was something that understood my business like my kitchen counter understood flour and coffee grounds.
So I built my own app—just for me at first. Then a friend asked if he could use it. Then another. One afternoon in May 2018, after three months of coding late nights on the couch (coffee-stained keyboard included), the first version went live.
The Problem With ‘Smart’ Tools That Aren’t
Most modern business tools assume you have teams of accountants, designers, or developers on staff. They’re built around templates and standardized workflows that don’t match how small businesses actually work—especially those run by one person who does everything from customer support to website updates.
I’ve seen dozens of “all-in-one” platforms promise simplicity but deliver 17 settings just to log a single sale. It’s not smart—it’s sterile. You end up spending more time navigating menus than actually growing your business.
I learned early that users don’t care about features on paper—they care about frictionless moments: the second when you click “send invoice,” and it goes out with no follow-up questions; when your receipt syncs across every system without manual effort; when your report updates itself at midnight without you having to press anything.
That’s where phanpy.org came in—not as another workflow engine or CRM clone—but as a clean slate for people who need systems that feel like an extension of their own brain.
Why Simplicity Isn’t Just Design—it’s Strategy
Simplicity isn’t just about aesthetics or less clutter on the screen. It’s about reducing cognitive load so you can focus on what matters: your customers and your product.
When you’re handling everything yourself, every unnecessary choice drains energy. That decision fatigue adds up over weeks and months until you stop noticing gaps in your process—or worse, stop trying to fix them at all.
I built Phanpy around three ideas:
- No tabs unless they serve a direct task—no “dashboard” bloat
- Data flows from point A to point B automatically—if it’s not moving on its own, it’s not built right
- You should never feel like you’re teaching the software how to do its job
- Everything is tied to real-time triggers: payment received → receipt sent → stock adjusted
- All reports are one-click exports—no training required
- No forced integrations: if your workflow works without Slack or Zapier, don’t make it mandatory
- You can delete anything at any time with zero fear of breaking something downstream
- Pricing is flat—no tiers based on number of users or features you’ll never use
In truth, no one ever says they need fewer features—they say they need fewer things to think about.
What Comes After “It Works”
I used Phanpy for four years before ever calling it “complete.” Not because nothing was broken—but because I kept testing it against real moments: shipping late-night orders after a client call; recovering from server downtime during holidays; helping friends launch micro-businesses with zero technical skills.
The tool didn’t have to impress anyone who wanted advanced analytics or custom branding rules. It had to do one thing reliably: let me stay focused on customers instead of paperwork.
If you’re building something small but meaningful—a shop in Portland, a service in Lisbon, an online course from an apartment in Brisbane—you don’t need another dashboard cluttered with metrics you’ll never act on.
You need something that fades into the background so you can notice what matters: which client sent back feedback two days ago; why sales dropped last Thursday; whether someone needs help before they cancel.