Your team is doing the same work twice.
Booking requests, customer updates, and reporting can become a chain of spreadsheets and manual handoffs. We can map the workflow and find where a small integration or internal tool would help.
Syracuse, Utah · Consulting through NexSolvo
I’m Joe Billman, a software development leader and founder with 20+ years of experience. I help businesses work through software decisions, improve manual workflows, and shape ideas into useful products.
Where I can help
Booking requests, customer updates, and reporting can become a chain of spreadsheets and manual handoffs. We can map the workflow and find where a small integration or internal tool would help.
I bring product, UX, and engineering experience to help identify the user, the core problem, and the first version worth building.
An AI-assisted prototype can make an idea tangible. The next questions are about real users, data, permissions, failures, and how the product will be supported.
A practical decision guide
Start with what already works. These options can fit together: an existing product, one useful integration, and a small custom tool may be enough.
The problem is common.
Start with an existing product when it covers the essential workflow. Compare the subscription, setup, and training costs with the cost of maintaining your own software.
For example: A standard appointment scheduler may be all you need.
The tools work. The handoffs don’t.
Keep the systems your team already knows and connect them. First check whether their integrations or APIs support the data you need to move.
For example: Send a booking request into your customer management system.
The same work repeats.
Define the rules, exceptions, and person responsible before automating a task. Use AI where interpretation helps, with review for decisions that need human judgment.
For example: Prepare a follow-up draft for someone to review and send.
Your workflow needs something different.
Consider custom software when existing tools leave an important gap. Scope the smallest useful version, including who will operate and maintain it after launch.
For example: Combine rental availability, fit requirements, and booking status.
AI prototype → working product
I use AI-assisted tools to reduce friction in development. Engineering judgment still matters when people depend on the result.
Read my approach to AI-assisted development →The answers help define a review and the next phase of work. They’re a starting point, not a certification of launch readiness.
Built and operated firsthand
These are my own ventures. They show how I connect product decisions, customer experience, and the systems behind the scenes.
Local business operations
A Syracuse-based rental business with a website and operational tools built around how a booking actually works.
Learning and product development
A game-based learning platform that brings together my background in educational software, games, and product design.
For my engineering leadership and work history, read my resume.
Working together
Consulting engagements are through NexSolvo LLC, my company. I’m based in Syracuse, serving Northern Utah and remote teams.
Tell me what you’re trying to improve, the tools you use, and any timing or budget constraints. Plain language is welcome.
We’ll clarify the problem and discuss whether an existing tool, an integration, a review, or a scoped build makes sense.
Before implementation, define the deliverables, responsibilities, and what success should look like. Include the plan for operating and maintaining the result.
Before you reach out
Yes. I’m based in Syracuse and work with businesses across Northern Utah, including Davis County, Layton, Farmington, and Ogden, as well as remote teams. Share your location and preferred way of working when you reach out.
Describe what you want to improve, who uses the current process, and where it breaks down. A list of your tools and a rough budget or deadline helps. You don’t need a technical specification to start.
Yes. We can discuss what works, what is still uncertain, and what needs review before real users depend on it. The next step depends on the code, data, integrations, and risks involved; a working demo alone doesn’t establish launch readiness.
Scope, integrations, data migration, permissions, and reliability requirements all affect cost. Hosting and ongoing maintenance matter too. We can discuss a smaller first phase and agree on scope before committing to a build.
Maintenance, hosting responsibilities, documentation, and any ongoing support should be part of the project scope. We’ll discuss what your team can own and what help you may need before choosing an approach.
NexSolvo LLC is my company, and consulting engagements are handled through NexSolvo. This site shares my background and project experience; NexSolvo is where you can explore services and start a project conversation.
Let’s work through it
A rough idea or a frustrating workflow is enough to start. Tell me about it, and we can discuss a practical next step.