For owners of 4–20 short-term rentals

Run the portfolio. Not the inbox.

A custom AI back-office, built around the stack you already use, live in 3–4 weeks. Guest messaging, pricing checks, reviews, maintenance — handled by a system designed around how you actually operate, not how a SaaS product thinks you should.

Three ways to engage · Live in 3–4 weeks · Built around your existing stack · Charlotte, NC · Microsoft Partner verified
01 — Operators

Don't take my word for any of this.

Justin walked me through what was possible in 20 minutes and it was the clearest conversation I've ever had about this stuff. I run four Airbnbs and now I can actually see what to build first.

Joe Hager
Short-term rental operator · 4 properties

More named references are available on the call — including operators currently mid-build under NDA, and a senior leader at a Fortune 500 industrial real estate platform where I led operational excellence and AI adoption for six years.

References on request
The next named study ships to /work when an operator signs off.
02 — Sound familiar

If any of this is your actual week, we should talk.

i.
A guest sends a 2am message about the AC, three reviews need responses before checkin, and the cleaner just texted that the linens were short again. The cost: a 4-star review tomorrow, and a search-rank ding the algorithm won't tell you about.
ii.
You set pricing on Sunday night and you already know you're either leaving money on the table or chasing the comp set down. Either way, it's a guess. The cost: a season's worth of mispriced nights compounds into a number you don't want to see in December.
iii.
The cleaner texts "I'm here but the lockbox isn't working" and you're in a meeting with no way to help. The cost: a turn day that runs late and a checkin guest who notices.
iv.
Three guests this month asked the same question about parking. You wrote three slightly different answers, each one a little less patient than the last. The cost: tone drift the guest reads, and a review that mentions you "seemed annoyed."
v.
A maintenance request came in three weeks ago. You can't remember if you sent it to the vendor. You scroll back through the thread anyway. The cost: the same thing breaks again at the worst possible time.
vi.
A 4-star review just landed. The reason is something you actually fixed last month. Now you need to write a response that doesn't sound defensive. The cost: the new fix never gets credit, and the next guest reads the unanswered complaint first.
03 — What it looks like

Guest messaging, before and after.

One workflow shown end to end. The same shape applies to pricing, reviews, maintenance, the books, and the rest.

Before

Your phone is the system.

Messages come in across Airbnb, VRBO, Hospitable, SMS, and email. You answer them yourself, or your assistant does, or nobody does in time and the review reflects it.

Common questions get the same answer typed for the hundredth time. Hard questions wait until you have a minute. 2am messages get answered at 7am, or not at all.

Every conversation lives on its own platform, in its own thread, in its own inbox. There's no record. There's no way to see how well you're actually doing.

After

You stop being the inbox.

You sleep through the 2am wifi questions. A trained agent with your house rules, voice, and FAQ handles the routine layer — checkin instructions, neighborhood questions, lockbox codes — in seconds, in your tone, around the clock.

The messages that actually need you wait in a single queue with a draft response ready for one-click approval. You answer the important things faster — not more of them.

On Sunday morning you open one view and see what guests asked this week, where the friction is, and what's worth fixing next — instead of scrolling five inboxes for an hour to feel "caught up."

If this is the shape of what you need, the next step is short.

Book a call →
04 — Three ways to engage

Pick the relationship, not just the deliverable.

05 — Honest comparison

Why this, instead of the obvious alternatives.

DIY + a VA Off-the-shelf SaaS NexStride custom
Setup time Ongoing forever 2–4 weeks of you adapting 3–4 weeks, then done
Monthly cost ~$1,200 VA + tools $400–$800 in subscriptions $0 if you self-run, or a hosted fee
Built around your stack? Sort of. The VA improvises. No — you adapt to it Yes. Always.
Who owns the system? You + the VA's memory The vendor You do.
What breaks at 15 properties? The VA Pricing tiers, feature gaps The system rebuilds with you
When things go wrong at 2am You handle it You file a support ticket The agent drafts, you approve
06 — About
Short version of who you'd be working with.

I'm an operational excellence leader by day and a 0-to-1 builder by night. Six years running operational excellence and AI adoption at a Fortune 500 real estate company. Before that, Lean leadership in two major health systems.

I ship software, not slides. FieldPilot, a decision system for field sales teams. Fillr, a pay-per-slot scheduling product for service businesses. Both live, both shipping to real customers.

I'm not a consultancy that subcontracts the build. I am the build.

See the full work →
07 — Common questions

Things people ask first.

What does this cost?
Pricing depends on which engagement option you pick — Full Custom (you own outright, in your market), Design Partner (half the upfront fee, I retain the right to commercialize a generalized version later), or Build & Host (reduced upfront, monthly recurring). All three are discussed on the call, with a one-page fixed-scope, fixed-fee proposal in writing within a few days. A published price grid would lie — every portfolio's stack and constraint set is different.
If I'm a Design Partner, what do you do with what you learn?
I retain the right to build a generalized version of the pattern — without your data, your customer list, or anything proprietary to your operation — and sell it to others. You keep a perpetual license to the version we built for you, including the configuration unique to your portfolio. In your specific market, there's a written carve-out so I'm not selling the same thing across the street.
How small is too small?
If you have at least one workflow eating more than two hours a week and you can describe it clearly, you're not too small. The sweet spot is 4–20 properties. Useful systems can be built for operators with one well-loved property, but the ROI math gets thin below four.
Do I need to know anything about AI?
No. Knowing your workflow is the prerequisite — not knowing the technology. If you can describe what currently happens and what should happen, I can build the system. I'll teach you what you need to run it confidently.
What happens when the AI gets something wrong?
Every system I build has a human review layer for anything material — guest comms, payments, money decisions. The agent drafts. You approve. As it proves itself on specific task types, we expand its autonomy. Nothing ships that can quietly fail on you.
My PMS / cleaner / accountant already uses [tool]. Will this conflict?
Almost never. Most of what I build sits on top of your existing tools — Hospitable, Hostfully, AppFolio, QuickBooks, Gmail, your spreadsheets — and connects them in ways the tools themselves don't. We design around your stack on the call.
Where does my data live?
By default, in your accounts on your infrastructure, under your control. If you'd rather I host the system, your data lives on infrastructure I run under a written agreement on retention, access, and deletion. Your data is never used to train models. It's never shared.
What's the smallest project worth doing?
One high-leverage workflow, built and live in two to three weeks. If we get on the call and the honest answer is "you don't need me — here's the off-the-shelf tool that does this," I'll say that. The goal is leverage in your operation, not maximizing my invoice.

Tell me what's eating your week.

A 30-minute call. You describe the workflow. I tell you what I'd build, how long it would take, and what it would cost. Or I tell you that you don't need me, and what to use instead.

Book a call →
Or email jide@nexstrideconsulting.com · Typical reply within 48 hours · Charlotte, NC