Questions I hear often
Questions leaders ask before changing how work gets done.
These questions are normal. The first call is designed to help determine whether automation, AI, workflow redesign, or a simpler process change is the right next move.
Decision support
Frequently Asked Questions
Who's a good fit for Smith Revenue Strategy?
Consultants, contractors, and privately held businesses with revenues ranging from $500,000 to $100M.
What is your pricing model?
Every engagement starts with a consult to discuss your situation and consider existing roadblocks and constraints. Pricing may include project-based work and consulting, custom solution design or setup fees with an ongoing support tier, or fractional leadership.
What if our business is too messy for automation?
Messy is actually a good starting point. You don't need a fully clean operation. You need one repeatable task you'd like off your team's plate. That's where it starts, and it builds from there.
When is a company ready for automated workflows?
If your team is doing the same work over and over manually, you're ready. Automation isn't about replacing people. It's about freeing them to focus on work that actually requires human judgment.
What if our business has too many nuances?
AI thrives in the nuance because it has a lot of range as long as the driver has the vision. If you have the vision, AI can be an excellent partner in bringing it out into reality.
Can AI be consistent enough for core business functions?
Predictions and machine learning can be inaccurate, but that is generally avoidable during a curation phase. Humans have been known to be inaccurate as well. The benefit of the LLM is that you can curate multiple ML models and see which one is most accurate for your intended purpose.
Do we have to send business data to public AI tools?
No. There are private AI options that keep your data internal and off any public model. Cloud providers also offer private environments where your data isn't used to train anything. The right setup depends on your security requirements, and that's part of what I help you figure out.
Do you use AI to do our work?
Yes, and here's exactly how. I use AI tools for the organizing, drafting, and research work. That's what they're good at. But everything you get from me, I've read and I stand behind. The composition gets automated. The accountability doesn't. If a recommendation reaches you, it's because I thought it through, not because a model produced it and I forwarded it.
What about security risk?
This is not a new category of risk. It is the same risk you already manage with the software and operating systems you run today. The real question is whether you have a clear policy for who can reach what data. If you do, AI gets held to it. If you don't, that is the first thing we fix.
Can regulated industries use AI solutions?
Most providers have compliance-compliant tenant environments. Hosting an LLM locally is also a capability, though it can drive up infrastructure cost. The tradeoff is that you have full and total control of your data.
What if our software is old and hard to integrate?
This is not a new problem. The build-vs-buy decision has always been there, and now the shift to building is more obtainable. Rather than using a solution that inhibits revenue growth, investing in a solution custom tailored to your environment can provide more business and process control that influences efficient operations.
Have you actually built one of these, or do you only advise?
Both. Most of this work makes better use of the tools you already own. When nothing on the market fits, I build. BidStrike is mine: it scores bid invitations for contractors so estimators stop losing their week to sorting through them. I own it outright, so treat it as a work sample and not a referral.
Learn about
What if the technology keeps changing?
It will. That's why I focus on process first and tools second. The businesses that adapt well aren't the ones with the newest software. They're the ones with clear processes that aren't locked to one vendor. I build for that flexibility from the start.
What if we do not have technical people to manage this after launch?
Managed service providers and support contracts are not a new concept, and they should be looked at through what is best for your company. Some companies have the personnel to fine tune agentic automations while others are solo shops. The solution delivered needs to be built so you do not need daily fine tuning.
We already have ChatGPT or Microsoft Copilot. Why work with SRS?
ChatGPT and Copilot are great for individual productivity: drafting, looking things up, answering questions. What I focus on is different: connecting your systems, automating handoffs between teams, and building workflows that run without someone prompting them every time. Those are separate problems, and separate tools.