Loading Donald Lena…
Custom software · Automation · Operating strategy
One place
to run the job.
I build software for contractors and local services. Each system follows the real work, from the first call to final payment.
- Estimate
- Schedule
- Do the work
- Invoice
- Collect & review
01 / MetroGlass Pro
Built for an actual field sequence.A glass job carries a lot more than an invoice.
The customer promise, the measurements, the costs and the money belong to the same job.
I built MetroGlass Pro OS around the sequence of a glass job. One record held the scope and specifications, install date, direct expenses and receipt images, deposit, PDF invoice, Stripe payment link and next action. Its Supabase database was deleted, so the internal app is no longer usable. This case documents what I built.
Ways to work together
Start where the handoff breaks.Custom job systems
Connect the tools you use, or build a new home for estimates, work, costs and collection.
02 / Focused serviceAI phone reception
A bounded first response for missed calls, with approved answers and a human handoff. Pilot availability.
03 / Focused buildJob costs & invoices
Connect PDF billing, direct expenses, receipts and payment status to the job behind them.
The method
Start with one real workflow. Let the system evolve.
I look at how work arrives, moves through the team and gets paid. The first useful change might be clearer local marketing, a better management routine, a focused automation or custom software. We keep what already works and build where the real gap remains.
Begin with an operating reviewMore work
Different contexts. The same close attention.Le Yard
A restaurant on Ninth Avenue, and the software taking shape with it.
Ramerino
Real service moments shaped into a recognizable restaurant presence.
Tea and Milk
Clearer photography and a more useful first impression on Maps.
Also building with Lokeil Remodeling · Private software for Prestige Lounge, Brooklyn.

A note from Donald
Useful software starts with paying attention.
I work with the people doing the job to understand the details a generic tool misses. The goal is a calm system the team can actually use, with room to grow.
A little more about meSomething getting lost between steps?
Let’s look at the workflow.
Tell me where the work slows down. I’ll suggest a useful first step.


