EQUIBOX Design Decisions: Sunny Booths, iPads, No Signal, True PDFs

In short: The EQUIBOX 3D quoting tool was designed for where the selling happens: sunny booths, an iPad, agricultural shows with no signal. That's why it has an offline queue that never duplicates contacts, a lighter 3D for tablets, a deliberately exaggerated night mode and a PDF built from the same rendering the customer saw.

When I built the 3D quoting tool for EQUIBOX, the horse barn manufacturer in Berazategui, Buenos Aires, half the decisions didn't come from the technology but from where it gets used: a booth at an agricultural show, in the sun, with an iPad in hand and no signal. Here I explain them in business terms: what problem each one solves.

If you're looking for the overview of the system (public quoting tool, sales panel, CRM), it's in the EQUIBOX case study. Here I'm covering what you don't see.

Why a quoting tool for the countryside has to work offline

At an agricultural show the signal comes and goes, and the worst case is when it seems to work but every request takes a minute and then fails. A quoting tool that depends on internet goes down exactly when there are people at the booth, and the farm owner is there now, not tomorrow.

The decision was to make the system an installable app that works fully offline. The entire application is stored on the device, so the iPad opens the quoting tool even without a single bar of signal. I cover the topic more generally in offline 3D quoting tools.

An offline queue that never duplicates a contact

Getting the app to open with no signal is the easy part. Each quote is first saved on the device, in a local queue, and when the connection comes back it's sent automatically. The problem shows up with an intermittent signal: the iPad sends the quote, the server receives and saves it, but the response gets lost on the way back. As far as the device knows, the send failed. So it retries. And the server receives the same quote twice.

If you don't solve that, the CRM ends up with the same customer entered two or three times, two sales reps calling the same person, and reports counting requests that don't exist.

The solution is for every quote to be born with its own identifier, generated on the device, and for the database to refuse two records with the same one. If a retry arrives for something already saved, the database recognizes it and doesn't duplicate it. The contact exists only once in the CRM.

For the manufacturer, follow-up after a show starts with a clean list, which is what makes a CRM for manufacturers reliable.

Smooth 3D on an iPad

A rendering with wood textures, shadows and lights runs fine on a computer; on an iPad it can stutter. And 3D that stutters in front of the customer sends exactly the opposite message from the one you want.

The decisions I made:

• A resolution cap on touch screens. Drawing every pixel on a tablet isn't noticeable to the eye, but it is noticeable in smoothness.
• Shadows calculated only once. The barn doesn't move while the customer rotates it, so shadows don't need to be recalculated every frame.
• A maximum number of lights at night. Every light that's on has a cost; there's a cap that's enough for night mode to look lit without the iPad struggling.
• A visual limit on stalls per group that doesn't limit what can be quoted. If someone quotes a very long row, the rendering shows a representative section, but the quote carries the real quantity. What you see and what you're charged are deliberately kept separate.
• A camera that reframes itself based on the size of the layout. Going from 2 stalls to a U-shaped plan doesn't leave the barn cut off the screen.

The general principle is in why a 3D quoting tool has to work on a phone: the device the sales rep and the buyer are holding is the one that matters, not the one in the office.

A deliberately exaggerated night mode

The quoting tool has a day mode and a night mode. In night mode, the lights in each stall turn on. Seen in an office, it looks overdone: darker, and with more pronounced lights than would be realistic.

That's intentional. The quoting tool is used at booths in direct sun, with glare on the screen. A "correct" night mode would look, in full sun, like a gray screen where you can't make anything out. Exaggerated, the contrast holds up against the glare and the customer sees what matters: that each stall has its own light and what the barn looks like lit up.

It's a decision that doesn't come from any design guideline, but from standing at the booth looking at the screen. With the same reasoning, the interface is neutral, so the only color is the wood, and it uses a single typeface to load fast on a weak signal.

A public backend that's still locked down

The public quoting tool lets people request a quote without creating an account, because asking a buyer to register means losing inquiries. But a system where anyone can write to the database needs care.

I solved it by putting security in the database, not just in the interface:

• Access rules in the database itself. The public can only create a request; they can't read other people's requests or see prices. Permissions and policies are treated as two separate layers, so a failure in one doesn't open everything up.
• A request limit per IP and per device. Anyone trying to flood the CRM with fake requests hits a cap.
• The notification email is built on the server. Every quote triggers an automatic email to the manufacturer, but that email is assembled on the server side from the request's identifier. Nobody can use the manufacturer's system from the outside to send an email with made-up content.

For the owner, this means the quoting tool is open to the public while prices, customers and sales reps stay private.

A PDF that shows what was quoted

The PDF quote includes the isometric view and the floor plan of the barn, taken from the same rendering the customer saw, plus photos of the selected accessories. It's generated in the browser as a vector PDF, so the text stays sharp whether it's printed or zoomed in.

The key decision is where the images come from. With catalog photos of similar barns, the PDF would show a different number of stalls, a different layout, different walls: the customer signs while looking at something that isn't their product, and the difference shows up when the truck arrives.

With views taken from the same rendering, what the customer saw on screen, what the quote says and what production receives are all the same configuration. That's the central argument of automatic PDF quotes and from quote to production.

None of these decisions shows up on a feature list. They're answers to "what happens if...?": if the signal drops, if it's sunny, if someone abuses the form, if the PDF doesn't match what was sold.

The 3D engine that was born at EQUIBOX is the one I now use in Estructuras 3D; you can try the horse stable configurator, which uses the same geometry. And if you sell at trade shows, on job sites or out in the countryside and want to see how your product would look, message me on WhatsApp at +54 9 11 6193-3176 or email facundocampo100@gmail.com. What I offer is described on the custom 3D quoting software page.

Frequently asked questions

What happens if the internet drops in the middle of a quote?

The quote is still saved on the device. When the signal comes back it's sent automatically, and because each one carries a unique identifier created on the device, it's recorded only once in the CRM, no matter how many times it's retried.

Does the EQUIBOX 3D quoting tool work on a tablet?

Yes, it was designed to be used on an iPad at agricultural shows. It has a resolution cap on touch screens, shadows calculated once, a maximum number of lights in night mode and a camera that reframes itself, so the 3D runs smoothly.

Why does night mode look so dark?

Because it's used at booths in the sun. A realistic night mode, with glare on the screen, would be impossible to make out. Exaggerated, the contrast holds and the customer sees what the barn looks like with the lights in each stall turned on.

Who made these design decisions?

Facundo Campo, who designed and built the entire EQUIBOX system, from the 3D rendering to the backend.