We would rather show the work than describe it. Here is what went into production this month, and what each thing is actually for.
Four properties, one design system
The group's four web properties relaunched together: apex-intelligence.co (the parent), apex-intel.co (the product lab), digi-mkt.co (the growth practice) and apex-pay.co (payments).
They share one stylesheet, one type system and one component set. That is not a cosmetic decision. It means a change to how a card or a nav behaves ships to four sites at once, and a new page starts from a system rather than from a blank file.
Apex Pay, live as a Maverick Payments partner
The payments company is live as a registered partner of Maverick Payments. Acceptance runs on Maverick's certified infrastructure — card data never touches Apex servers — while we build the merchant experience on top: guided applications, hosted payment flows, and daily reconciliation.
There is a public sandbox where merchants and partners can exercise both flows with test cards before anything goes live.
A phone line that behaves like a system
Calls into the main line now route through an IVR, record, and produce a transcript. The point is not the automation — it is that a call arriving after hours lands somewhere with an owner attached, instead of in a voicemail box nobody checks until Tuesday.
Five dealer sandboxes
The automotive work runs as live sandboxes rather than slide decks:
- AutoScope — dealer merchandising and inventory intelligence, the product the automotive arm is built around.
- Lane Watch — lane-level market movement, watched continuously instead of pulled once a week.
- Manheim read — auction data read and reconciled against live inventory positions.
- Pricing — pricing scenarios modelled against real stock rather than a spreadsheet of guesses.
- Reporting — the weekly report that used to be rebuilt by hand, assembled from the project record instead.
The thing underneath all of it
Every item above was built and launched through the same loop — ask, build, verify, remember, improve — enforced by miOS rather than by anyone's discipline.
That is why this post could be written from records instead of from memory. The deploy records, the status checks and the screenshots were filed against their projects at the time, which is the only reason a month-end summary is a ten-minute job rather than a reconstruction.
What is next
Direction rather than dates, because anything with a date on it is something a client is already waiting on:
- miosai.co — miOS gets its own home, with documentation and an SDK surface, so teams can build on the layer instead of only buying outcomes from it.
- A wider agent library, so a new operation starts with a trained team rather than an empty workspace.
- Deeper automotive — the sandboxes above graduating into one product surface for franchise, independent and group rooftops.
- Self-serve payments — qualification and gateway provisioning a merchant can complete without waiting on a human in the loop.