Question 1

How do your engagements work?

Accepted Answer

Three tiers. Operations Audit is a $2,500, roughly two-week paid diagnostic — process mapping, stack inventory, written audit, prioritized recommendations. Operator-Led Build is a fixed-scope custom build, typically $12,000–$50,000+ over 4–8 weeks. Embedded Operations is a monthly retainer ($8,000–$15,000/mo) where I act as your fractional ops architect on an ongoing basis. Most engagements start with the smaller tier and earn the next step.

Question 2

Why no $1,500 starter tier?

Accepted Answer

At that price the work is usually a single Zap or one simple integration — and you're better off either doing it yourself with off-the-shelf tools or hiring through Zapier's expert directory. My work is more useful at the level where there's actually a system to design, not just a workflow to glue.

Question 3

Is the Operations Audit fee credited toward a build?

Accepted Answer

Yes. If you decide to move forward with an Operator-Led Build after the audit, the $2,500 audit fee is credited toward the build. So in practice the audit is risk-free if a build follows.

Question 4

Do you offer custom pricing for larger or longer engagements?

Accepted Answer

Yes. Anything beyond a single Operator-Led Build typically rolls into Embedded Operations on a multi-month retainer. Large multi-system rollouts or longer operations-architecture engagements get scoped individually.

Question 5

How long does a typical engagement take?

Accepted Answer

Operations Audit: about two weeks. Operator-Led Build: usually 4–8 weeks depending on scope and integrations. Embedded Operations: ongoing, with a 3-month minimum.

Question 6

What does the actual process look like?

Accepted Answer

Discovery (process and stack walk-through), Design (what we'll build, what we won't, and why), Build (software, integrations, dashboards, documentation), Rollout (training, monitoring, iteration). The same four steps whether you're at $2,500 or $50,000 — only the scope of the build changes.

Question 7

Do you provide training and documentation?

Accepted Answer

Yes. Operating documentation and user training are always included with builds. For complex systems I'll also produce a runbook so your team can debug and extend without me.

Question 8

Who do you typically work with?

Accepted Answer

Primary focus is real-estate operators — property managers, multi-family operators, real-estate investors, small brokerages. I also work with construction back-offices (subcontractors and specialty contractors) and transactional law firms (real estate, immigration, estate planning, high-volume practices).

Question 9

Do you work outside those verticals?

Accepted Answer

Yes, but selectively. The pattern I look for is operations-heavy SMB with a messy back office and a real budget for fixing it. If that's you, even outside the named verticals, reach out — but expect the conversation to start with whether I'm the right fit.

Question 10

How big does my company need to be?

Accepted Answer

Sweet spot is roughly 20–250 employees or $3M–$25M revenue. Smaller and you may not need custom software yet (Airtable + a few Zaps might be enough). Larger and you probably need a full-time head of operations or CIO, not me.

Question 11

Which tools do you work with?

Accepted Answer

I integrate with whatever you already pay for. Common: AppFolio, Buildium, Yardi, RentManager, Procore, QuickBooks for real-estate and construction. Clio, MyCase, PracticePanther for legal. Plus the usual horizontal stack — Airtable, Make, Zapier, OpenAI/Claude APIs, Twilio, DocuSign, Stripe, Salesforce, HubSpot.

Question 12

Will you replace my existing systems?

Accepted Answer

No — that's almost never the right move. The point is to make your existing stack cooperate. Custom software gets built when the existing tools genuinely can't carry the load, not as a default.

Question 13

Do you build with code, or just with no-code tools?

Accepted Answer

Both — picked by what the job actually needs. I have six years of production SaaS engineering background (Java, Python, microservices, Spark/Kafka, distributed systems), so when a custom app is the right answer, I build it properly. When Airtable + Make is genuinely sufficient, I'll tell you and build it that way.

Question 14

What kind of support comes with a build?

Accepted Answer

30 days of post-launch support is included with every Operator-Led Build. After that, you can roll into Embedded Operations for ongoing iteration, or contract for support per-issue.

Question 15

What happens if something breaks?

Accepted Answer

Monitoring and alerting are baked into every build, so I usually know about issues before you do. Retainer clients get fast-turnaround fixes. One-off builds get support per whatever terms we agreed to in the engagement.

Question 16

Can we add to the system later?

Accepted Answer

Yes — and that's the whole point of Embedded Operations. Many builds start as a single engagement and grow into a multi-feature operating backbone over a year or two.

Question 17

How do I get started?

Accepted Answer

Book a free 30-minute teardown. Bring one workflow that's costing you the most time. We'll talk through whether software can fix it. You leave with a recording and a candid take. From there it's either a paid Operations Audit, a direct build, or 'I don't think I'm the right fit, here's who might be.'

Question 18

Is the teardown call really free?

Accepted Answer

Yes. No obligation, no sales pitch dressed up as discovery. The goal is for both of us to figure out whether there's a fit. If there isn't, you've got a free consultation. If there is, you've already started the engagement.

Question 19

What should I bring to the teardown?

Accepted Answer

One specific workflow. Not a list, not 'we need to automate everything.' One thing — tenant maintenance triage, bid intake, owner reporting, lease abstraction, document chaos, whatever's actually costing you. The more concrete, the more useful the conversation.

Engagements, pricing, fit.