ComplianceTracker.io Project Story
The Origin Story
Back in the early days of SaaS, I was the Controller at a dog walking app, working out of a mansion in the Hollywood Hills. Nearly every week we were opening offices or hiring managers in a new city and state, and every time that happened, it fell to me to figure out what forms to file, which licenses to get, and when those deadlines were lurking. I became an accidental expert in compliance research—not because I wanted to, but because missing a permit or deadline could shut us down.
Fast forward to three weeks ago: I'm doing the exact same research for a new accounting client, manually digging through government websites like it's still 2016. That's when I asked Poe to help me build a tracker, and thirty minutes later, I had something that would have saved me hundreds of hours back in my controller days.
The lightbulb moment pinged: every single person starting a business goes through this same nightmare, and most of them don't have an accounting background to navigate it.
The Pivot
I was about two weeks into the hackathon, working on a FutureTools clone for bookkeepers, when I suddenly lost all interest in that and pivoted to ComplianceTracker.io. I figured that if Poe and I could create a local tracker in 30 minutes, it should not be a problem for bolt.new to build one that anyone in the US could use.
Spoiler alert: Ha, Ha, very funny. It was way harder than I had imagined.
The Technical Reality
Poe came through again with the basic design which I saved to a pdf and uploaded to bolt.new, which did a pretty good job getting the basics up. Then the technical gremlins arrived, and I learned my most valuable lesson of the entire hackathon.
The API Nightmare
- Connecting to Dappier's API turned into a nightmare
- bolt.new kept insisting everything was working when clearly it wasn't
- It started changing parts of my app I didn't want touched
- Had to roll back to an earlier version multiple times
I hired an UpWork developer, got frustrated when he couldn't help either, and only later realized the truth: it wasn't his fault, and it wasn't really the platform's fault either.
The Key Learning
I was trying to push a no-code tool way beyond what it was designed for. The hard reality hit me - no-code is fantastic for MVPs and prototypes, but when you need real integrations, complex logic, and precise control? You're going to hit walls.
That thirty-minute tracker that worked perfectly for one location? It was the perfect use case for no-code. A full-scale, multi-state compliance platform? That's where you start bumping into the ceiling.
The Silver Lining
On a lighter note, I asked bolt.new (Claude Sonnet 3.7) to write a humorous script for the video. It came out really good, so I uploaded it to InVideo AI. What those two did really tickles me. Hope you like it.
The Vision
The plan for the future is to:
- Get the app working well
- Monetize the free version with dappier ai
- Build out a paid pro version for those with more than one location
There's going to be an explosion of new small businesses, and they'll all face the same compliance nightmare I lived through in those Hollywood Hills days.
The difference is, now they won't have to spend weeks buried in government websites at 2 AM. They'll have ComplianceTracker.io, and that feels pretty good.
Built With
- 18
- ai
- autoprefixer
- axios
- css
- dappier
- dnd-kit
- form
- hook
- hot
- javascript
- lucide
- netlify
- postcss
- postgresql
- react
- router
- supabase
- tailwind
- toast
- typescript
- vite

Log in or sign up for Devpost to join the conversation.