One Store Owner Automated His Entire Delivery Process. Here's How.
You're paying for software, and someone - your customers, your team, or both - is still doing manual work every week.
That was the reality for Jeff Maconi. He runs MaconiSetupShop, a subscription service for iRacing sim racing setups. Subscribers paid monthly but had to manually download files from a website, then open a separate desktop app to sort everything into the right folders. The store and the app didn't talk to each other - and Jeff wanted to fix that. No calls, no massive budget, no six-month timeline. Here's how it went, start to finish.
The Problem
The manual workflow wasn't just inconvenient - it was a business risk. Every missed download was a support ticket. Every support ticket was a chance for a customer to question whether the subscription was worth it. Jeff was spending time answering "where's my setup?" messages instead of growing the business, and customers who fell behind on downloads felt like they weren't getting what they paid for.
The friction also made the product harder to recommend. Word of mouth is everything in the iRacing community, and "you have to remember to download it yourself each week" isn't a great pitch.
Jeff had one hard constraint from the start: no spyware-like behavior. Some competing tools in the iRacing space require full access to users' computers. Jeff sees this as a liability and a trust violation. Whatever we built had to be privacy-first and offline-capable. The desktop app should do its job and nothing else.
When "It Works Fine" Is Quietly Costing You
Jeff's workflow technically worked. Customers could get their setups. But "it works" and "it works well for the business" are different things, and the gap was slowly eating his time and his retention.
If you run a business with manual processes baked in, here are the signs that "works fine" is costing more than you think:
You keep answering the same question. If customers regularly ask how to do something that should be obvious, the process is broken, not the customer.
Customers have to do work to get value from what they paid for. A subscription should feel effortless. If yours requires a manual step every week, some percentage of your customers will quietly stop engaging. Not because your product is bad - because friction compounds and life gets in the way.
Your product comes with an asterisk. "It's great, but you have to..." kills word of mouth. People recommend things that just work.
You're spending time on support you shouldn't need. Every hour answering "how do I download this?" is an hour not spent on growth.
If any of that sounds familiar, the fix is often smaller than you'd expect. Jeff's full delivery automation was a 4-week project.
How We Started - Low-Risk Discovery, No Commitment
Jeff reached out via Discord, referred by a mutual connection in the iRacing community. All communication happened naturally over async DMs - no scheduling calls, no meetings.
We proposed a paid discovery phase: dig into the existing codebase, research Wix API feasibility, and deliver a fixed-price scope document. If Jeff moved forward, the discovery fee would be credited toward the build. If not, he'd walk away with a clear technical assessment for less than the cost of a dinner.
Discovery uncovered a key constraint: Wix's File Share addon doesn't expose direct download links via API. This meant we couldn't just pull files from the existing Wix downloads page programmatically. We needed an alternative file delivery path. This is exactly the kind of thing you want to find out before committing to a full build.
The discovery deliverable: a detailed scope of work and a fixed-price quote for Phase 1.
What We Built (and Why)
Every technical decision came back to three things: keep it cheap to run, keep it fast, and respect users' privacy.
Jeff's Wix site already handles subscriptions and payments. A lot of shops would tell you to scrap that and rebuild on a new platform. I think that's wasteful. If your sales platform works, you shouldn't have to migrate just to add features. So we built a lightweight API layer that plugs into Wix for authentication and subscription verification, and handles file delivery separately.
The API runs on infrastructure that costs Jeff almost nothing at his scale - he pays per request, not per server hour. No monthly hosting bills eating into margins. For a subscription business with a few hundred customers, that matters.
Remember the Wix limitation from discovery - no direct download links through their API? The workaround was straightforward: Jeff uploads each week's setup files to a second storage location alongside Wix. One extra step in his workflow, but it keeps the existing website completely untouched. Customers who prefer the old manual download can still use it. Zero disruption.
On the privacy side - this is something I care about as an engineer. I've seen too many apps that quietly phone home, track usage, or demand permissions they have no business requesting. Jeff felt the same way, and it's one of the reasons this project clicked from the start. His customers never have to wonder what the app is doing in the background, because the answer is nothing. Credentials are stored locally and encrypted. Account linking is opt-in. The app does its job and stays out of the way.
The Build - 4 Weeks, All Async
All communication happened over Discord DMs - no calls, no standups, no project management tools. Just messages back and forth as questions came up.
We extended Jeff's existing VB.NET desktop app, which was originally built by another developer. Having the source code was essential for building on what already worked rather than starting from scratch.
Weekly check-ins were natural and informal. Jeff would ask questions as they came up, and we'd respond within hours. No scheduled meetings, no status reports.
What changed for Jeff's customers:
- Link your store account to the app once, and every future purchase downloads automatically
- Setups are filtered by subscription tier - you only see what you're paying for
- Browse available setups inside the app and check out seamlessly through the website
- Car names and season configs update on their own - no manual data entry when iRacing releases new content
- One active session per account, so Jeff's subscription revenue stays protected
Testing and Launch
Jeff tested for about a week with real setup files and real subscription tiers. Changes that came up during testing were handled same-day - the kind of responsiveness that matters more than rigid sprint cycles.
After testing wrapped, Jeff gave the green light to launch. His exact words: "Alright, I think we are good to launch!"
The Result
Before, Jeff's active subscribers had to remember to visit the website each week, download a ZIP file, open a separate app, and sort everything into the right folders. If they forgot a week, they'd message Jeff. If they fell behind, they'd start wondering whether the subscription was worth keeping.
Now they link their account once and every purchase lands in the right place automatically. No downloads to remember, no files to sort, no "where's my setup?" messages clogging up Jeff's inbox.
The manual flow still works for anyone who prefers it - nothing was taken away. Jeff has an ongoing retainer for maintenance and content updates, and background sync is scoped as a future add-on whenever he's ready.
For Jeff, the time he used to spend on support is now spent on the business. For his customers, the subscription finally feels like what they're paying for: something that just works.
"Harinder and his crew did a phenomenal job updating our existing program, and worked with us throughout the process to ensure that the final product was exactly what our business required. Thanks to his efforts, we were able to overhaul our software package, and provide our customers with an effective and easy to use update that greatly improved their user experience!"
- Jeff Maconi, Founder of MaconiSetupShop
What It's Like Working With Us
If you're a small business owner reading this and wondering whether this kind of project is realistic for your budget and timeline, here's what the MaconiSetupShop engagement looked like in practice:
-
Start small - A low-cost discovery phase proves feasibility before you commit to a full build. If the project isn't viable, you find out early and cheap.
-
Fixed pricing - The full Phase 1 build was a fixed-price contract, split 50/50 (deposit and delivery). No hourly billing, no scope creep surprises.
-
Async-first - We worked entirely over Discord DMs. No mandatory calls, no project management overhead, no waiting for the next standup to get an answer.
-
You keep everything - Full source code ownership. 30-day warranty. Ongoing retainer if you want it, but no lock-in.
-
We work with what you have - Jeff's existing Wix site, existing desktop app, existing customer base. We didn't ask him to start over. We connected the pieces he already had.
Running a business where customers or your team are still doing something by hand that should be automatic? Our discovery phase costs less than a dinner - and if you move forward, it's credited toward the build. Fill out the form below. It takes 30 seconds, and we'll get back to you within a day.