For months, everything was an order.
Someone fills out a form on the website? Order. A promotional offer sent to an existing customer? Order. A measured, priced, ready-to-schedule quote? Order. A confirmed job with a crew assigned and a date on the calendar? Also order. They all lived in the same table, wore the same clothes, showed up in the same list. The only difference was a status field that tried to carry the entire weight of a business's operational logic in a single string.
This is the quiet lie that early-stage software tells. When you're building fast, abstraction feels like efficiency. One model. One table. One list. Ship it. But the business doesn't think in abstractions. The office manager who answers the phone knows — in her body, before language catches up — that a new lead is a fundamentally different object than a confirmed Thursday job. They require different actions, different urgency, different screens. Flattening them into one list doesn't simplify her work. It makes her sort through everything to find anything.
The fix was a stage filter threaded through the entire stack. Request layer, API, frontend composable. Four values: lead, promo, quote, job. Four sidebar links. Four pages. Each one showing only what it should, with the columns and actions that stage demands.
But the ripple effects are where the real work lives.
The quote page — the customer-facing surface where someone decides whether to spend money — had been all-or-nothing. Here are five services. Accept them all or walk away. The update added checkboxes. Pick the three you want. Leave the two you don't. The call-to-action changed from "Place Order" to "Schedule Service" — a verb shift that sounds trivial until you realize "Place Order" sounds like buying something and "Schedule Service" sounds like getting something done. One implies a transaction. The other implies a relationship.
Products learned about application-specific pricing. First application of a season might be discounted to get someone in the door. Fourth application might cost more because it uses a different product mix. The widget shows expandable price breakdowns on each product card — not to overwhelm, but to answer the question the customer is already asking: why does this one cost more?
And underneath all of it, the email system — which had been quietly failing in production — got rebuilt. The queue moved from sync to redis, which meant emails stopped blocking HTTP requests. The SMTP port shifted to 2525 because a firewall was silently dropping connections on 587. MX records were corrected. Redis caches were split between beta and production so that clearing one didn't nuke the other.
Four infrastructure bugs. All interconnected. All invisible from the outside. The kind of thing where a customer says "I never got my quote email" and the answer is a chain that starts at a firewall rule and ends at a DNS record, with a race condition in the middle.
The Nebula theme arrived in the same session — navy-slate surfaces, blue-violet accents, CSS custom properties swappable through a composable. The marketing pages and auth screens got a visual identity that the rest of the platform was already wearing. But the theme is the surface. The real change happened underneath.
Software that treats everything the same isn't simple. It's confused. The moment you give each thing its real name — this is a lead, this is a quote, this is a job — the system starts to think the way the people using it already do. Clarity isn't a feature. It's the foundation that every feature needs to stand on.