From a brochure site to a storefront that takes orders.
ON-SITE rents cranes and heavy equipment to contractors who need a machine on site tomorrow. The business worked; the website could only ask you to call. You get the storefront that captures the quote, uploads the insurance, signs the agreement, holds the deposit and books the call, moved onto the domain overnight with zero downtime.
Real machines. No way to order one.
A WordPress brochure: browse a few photos, then pick up the phone. Every quote, insurance certificate, rental agreement and deposit moved by phone and email, and none of it was recorded anywhere the business could learn from.
The owner did not need marketing. He needed infrastructure that transacts. Sending traffic to the old site would have been paying to generate phone calls.
The storefront, and the plumbing under it.
Thirty-seven routes, no pricing anywhere on the public site, and a quote captured on the first click rather than the second.
- Equipment listings with real availability, replacing the brochure
- A two-field quote popup on every page, so a plain nav click on a machine page still records that machine
- Insurance upload and verification inside the order flow
- E-signature on the rental agreement, a deposit held on card, and an owner approval step before any charge fires
- A booking page with two calendars routed by channel, so a call booked from a Google ad is counted against Google in the CRM itself
- Terms and privacy written for what Google Ads review and the SMS carrier registration actually check
- A tracking number on every page and in the business schema, so calls attribute like everything else
Live overnight. Nothing dropped.
Backup taken, the full DNS zone inventoried, a duplicate mail record that had been silently violating the spec deleted, the new zone built with every record in place so the old site kept serving through the nameserver change, then apex and www flipped to the new site as the final step. Mail verified intact from outside after every step.
That is the standard for a domain move: you find out it happened because the site is different in the morning, not because your email stopped.
Vendor one of many.
The storefront and the MachineryMaps marketplace are the same codebase, architected multi-vendor from day one. ON-SITE launches as vendor one and proves the model on its own fleet. Next on this engagement is the Scale side: Google Ads onto a site that can now take the order.
More of the work.
Every engagement on this site is written up with its numbers. Totals, never monthly run rates.
MachineryMaps
The marketplace underneath ON-SITE, architected for many vendors from day one.
Read the case study ›Expert Health
A telehealth brand built from zero and run daily, our own.
Read the case study ›Smart Sellers Academy
Zero infrastructure to a complete system with a live KPI warehouse, still running.
Read the case study ›Acquisition Network
From zero to a full engine, then a clean exit with the system still running.
Read the case study ›Find out what has to be true before software helps.
If your site can only ask people to call, every dollar you spend sending them there is a phone call you may or may not answer. Thirty minutes and you will know what the first transacting version looks like.