Jacob —
You told me what you want, plainly: "I want everything automated. I want a message on my phone telling me where to drop off and where to pick up. I don't want to answer phones, I don't want to deal with Facebook messages, I don't want to do scheduling. I want this as hands-off as possible."
That is a real business model, and it is buildable. The hard part isn't any one piece — the platform handles inventory rentals, payment, and calendar booking out of the box. The hard part is the orchestration. Wiring 150+ individual automations together so that one customer tapping "book" on Tuesday at 11pm drives the entire chain through to a message on your phone Friday morning without you touching any part of it.
This document is the build plan. It walks through the seven systems we're wiring together, two narratives that show the orchestration in action, and what we're asking for to get started.
SüRJ is built around four pillars, in this order:
The scope below comes out of the second pillar — what we observed about how Boxless actually operates and what has to be true for it to run hands-off.
What looks from the outside like "a website with a booking form" is actually seven connected systems, each one configured, wired to the others, and tested against the real shape of your business.
Every customer interaction, every status change, every notification, every backend update — each one is its own automation, each one wired into the chain at exactly the right point. This is where the orchestration lives. This is what makes it hands-off.
A clean, mobile-first site that exists to do one job: take a customer from "I'm moving and need totes" to a confirmed, paid booking in under three minutes. Availability checker, rental configurator (tote count, dolly add-ons, packing paper, bubble wrap, rental length), instant quote, drop-off and pickup window selection, payment, confirmation screen. No phone call. No back-and-forth message thread. No human in the loop.
You already own the domain. We point it at the site and configure DNS through the platform.
The platform's rental engine handles the underlying inventory math — what's rented, what's available, what's in transit, what's coming back when. Our job is configuration: getting your 201 totes, your tote dollies, your furniture dollies, and your consumables (packing paper, bubble wrap, tape) loaded in correctly, priced correctly, and behaving correctly when a customer books.
Consumables flip to one-time-sale mode so they bypass the return logic but still hit the booking and invoice. Equipment categories are tagged so the booking flow only offers what's actually available for the requested window.
Card-on-file at booking through a tokenized integration via Electronic Payments, Inc. The rental fee charges at booking. A refundable damage hold is authorized separately and released automatically on a clean pickup, or converted to a damage charge if the post-pickup count comes up short or items return broken. No deposit calls. No "I'll Venmo you the difference" conversations.
Every booking moves through a custom pipeline. Each stage triggers its own automations on both sides:
At drop-off, you open the booking on your phone, snap a photo of the delivered totes at the customer's door, and tap "Delivered." That photo is automatically attached to the customer's record and sent to the customer in their drop-off confirmation text. Same pattern at pickup. You take the photo; the system does everything else with it.
Every message a customer would normally call, text, or DM you about goes out automatically: booking confirmation, day-before drop-off reminder with ETA window, drop-off complete with photo, mid-rental check-in with a one-click extension link, day-before pickup reminder, pickup complete with deposit-release notification, and a 48-hour-after thank-you with review request. Text and email. Branded to Boxless.
When a customer replies, ChatAI handles the common cases — extension requests, address changes, simple FAQs — and only escalates to you when something is genuinely unusual.
The Boxless phone number doesn't ring through to you. VoiceAI answers it, handles the common questions (pricing, area coverage, how it works, when you can drop off), captures booking intent, and routes to the website when a caller is ready to book. The only calls that ever reach you are the ones that genuinely require a human — and those come through pre-qualified.
Two views on your phone. The ops dashboard is your workday: today's stops in route order, customer name, address, gate codes, equipment count, tap-to-complete each step. The owner view is Monday-morning reality check: live utilization rate (% of 201 totes earning revenue right now), MTD revenue, upcoming bookings, repeat-customer rate, damage-hold conversion. One screen, real numbers, updates itself.
The clearest way to see what we're building is to walk through the same rental from two sides — what the customer experiences, and what you experience.
Total customer-facing interaction on your end for that rental: about ninety seconds of tapping. No phone calls. No DMs. No scheduling conversations. No invoicing.
Before we build the whole thing, here's where the customer site is headed. Same brand, same energy as the sticker, same "no boxes, no hassle" through-line. Click in and tap around — it's the early shape of the site, not the final pixel.
A single integrated build covering all seven systems, delivered over four to six weeks, followed by ongoing platform management. We work directly with you; this is not a hand-off.
Weeks 1–2. boxless.com site design and build. Rental engine configuration for the full equipment list. Payment processor integration through Electronic Payments. Phone number provisioned and A2P 10DLC registered. Platform sub-account configured end-to-end.
Weeks 3–4. The full 150+ automation library — every text, every email, every pipeline trigger, every backend update. ChatAI training on your common customer questions. VoiceAI configuration and call routing. Your mobile ops dashboard tuned to how you actually work in the field.
Weeks 5–6. Owner dashboard. End-to-end testing with live test rentals. A working session where we run a real booking through the system start to finish so you've watched it work before your first paying customer touches it.
You've shopped platforms before. You know what these line items cost individually. The $247/month covers all of it, with nothing else to pay separately:
If VoiceAI or SMS volume runs significantly above what a single-operator service business typically uses, we revisit. For typical Boxless volume, what's listed above is what you pay.
Boxless can run a compliant surcharge (matching what you're already doing in the wrap shop — 2% in Oklahoma) or dual pricing on the customer-facing checkout. Either offsets the build fee inside a year at modest booking volume. We'll pick the right one for Boxless in the working session.
I'm Steve Wilson, founder of Recherché Merchant Solutions and SüRJ. Twenty-five years in B2B consulting. Eight years in payment processing and merchant compliance. The last two years building custom web, CRM, and automation systems for businesses that have outgrown what got them here.
Boxless is the kind of operation SüRJ is built for — a real service business where the operator's time is the constraint, and the right automation turns one person into a team. We've done variations of this build for service operations across home services, fleet logistics, and rental inventory. The specifics are different; the playbook is the same.
The "Ask Porter" widget in the corner of this page is purpose-built for this proposal. Ask anything about the build, the seven systems, the 150+ automations, the timeline, what's included, what's not included, the payment side, the inventory logic — Porter is primed on all of it and answers in real English.
It's also a working demo of what the customer-facing assistant on boxless.com will do: handle the questions that would otherwise become phone calls or DMs, twenty-four hours a day, without you.
Thirty minutes on a screenshare. We walk through the build plan, you ask the questions you haven't asked yet, and we lock the start date. If you'd rather meet at your shop, I'm in OKC and happy to come to you.
Schedule the working session →If anything in the scope above doesn't fit how you actually want this to run, we adjust it before we build it — not after.
A working session — 30 minutes, screenshare, focused on locking the scope and start date.