We Started With a Problem, Not an App
If you've ever hired a plumber, electrician, or HVAC tech, you've probably noticed something. They're incredible at their craft and terrible at getting paid for it. Not because they don't deserve it, but because after a long day crawling under sinks and running wire, the last thing anyone wants to do is sit down and figure out invoicing software.
That's the gap CORELY is built to close.
Small trade operations, we're talking 1 to 5 person shops across New York City, are losing anywhere from 15 to 25% of their revenue every year. Not because the work wasn't done. Because it never got invoiced. Or the invoice sat in a pile. Or the follow-up never happened. The money was earned, it just never got collected.
CORELY exists as an enforcement layer. Work isn't complete until revenue is collected, and our job is to make sure that actually happens.
The Interface: Why We Built Three Buttons
Here's where most software products get it wrong. They try to solve every problem, and in doing so they create a new one: complexity.
We spent a lot of time thinking about who we're building for. These are tradespeople who finish a job at 6pm, hands dirty, standing in a driveway, maybe juggling tools and a phone call. They don't have time to navigate a dashboard.. And they don't want to learn a new system.
So we asked ourselves… What's the absolute minimum we need?
The answer was three buttons.
INVOICE — speak it, type it, or snap a photo of your notes. CORELY handles the rest.
MEDIA — document the job. Before and after photos, tied directly to the work order.(In development)
SUBMIT — one tap and you're done. The automation takes over.
That's it. We call it one-thumb operation. Everything is designed to work while tired, outdoors, on a cracked phone screen. Big buttons, no clutter, no learning curve.
What's Actually Happening Under the Hood
We're not going to get too deep into the technical weeds here, but here's the idea at a high level.
When an operator hits INVOICE and speaks into the phone, voice recognition converts what they said into a structured job record automatically. "Replaced water heater, four hours labor, parts were $340" becomes a formatted invoice without the operator typing a single word.
Photos taken through MEDIA get attached to that job and stored securely in the cloud, so there's always documentation if a customer disputes anything.
When SUBMIT gets tapped, the system handles delivery, follow-up, and payment tracking automatically. Digital payments get logged without any manual entry. Cash, check, or other payment methods can be logged in seconds so the full revenue picture is always visible.
The whole thing runs on a mobile-first architecture designed to be fast, reliable, and as invisible as possible. The operator shouldn't have to think about it. It should just work.
What We've Learned So Far
Honestly, the hardest part hasn't been the code. It's been restraint.
Early on, there's a temptation to keep adding. What about scheduling? What about a customer portal? What about reviews? All valid ideas, but every feature we add is another thing a tired plumber has to ignore.
We've had to kill features that were genuinely good ideas, just because they weren't the right ideas for right now. The discipline of staying focused on one outcome, revenue collected, has been the most important product decision we've made.
On the technical side, getting the Android app ready for internal testing has been a process. There are a lot of gates to clear before you can put an app in front of real users. None of it is hard, but all of it takes longer than you expect. We're working through the final steps now.
Where We Are
We're in alpha. The core app is built. The automation pipeline works. We're preparing to put it in the hands of our first five users, real NYC Tradesmen, through a concierge testing process where we stay close, watch what breaks, and fix it fast.
This isn't a soft launch with a landing page and a waitlist. It's a scrappy, hands-on test with people who are actually going to use this at work tomorrow morning.
The goal is to find out what "good enough to keep using" actually means for a trade operator, and then build toward that.
We'll keep sharing what we learn here. The wins, the pivots, the technical headaches. If you're building something in a similar space, or if you're a trade operator who sees yourself in any of this, we'd love to hear from you.
CORELY is being built in New York City for the people who keep it running.