Will it make things up?
It is set up to answer only from documents you gave it. It does not search the internet, and it is not asked to fill gaps from general knowledge. Every answer shows you the source, so checking it takes seconds. When it does not have the information, it is designed to say so rather than fill the gap.
No system is perfect, which is why a person approves everything before it leaves your office. That is not a disclaimer. It is the design.
Where does my data go? Is it training somebody's AI?
Your files stay yours. We do not use them to train public AI models, and the agreement says so. Access is controlled by role, the same way your file server is, so people see what they are supposed to see and nothing more.
We put the specifics in writing in the agreement, including where the data sits and who can reach it. If a vendor will not tell you that in writing, that tells you something.
Is this a setup to tell me to cut staff?
No. SageLogic is not in the business of helping firms eliminate people. We are in the business of putting tools in front of the people you already have so they can work more effectively inside the roles they already hold.
The firms we build for are usually behind on work, not overstaffed. If your problem is too many people, we are the wrong call.
What we build takes the repetitive part off your team so their hours go to the work that requires a licensed, experienced human. In most firms that means the backlog shrinks and the quality goes up, not that the payroll goes down. If a headcount reduction is your goal, say so in the first conversation and I will tell you that we are not the right firm.
What if it gets something wrong and it goes to a client?
It should not reach a client without a person reading it, and the systems we build do not send anything on their own. That is the point of the human approval step.
We also test for this before launch by deliberately trying to make it fail, and we train your staff specifically on how to recognize a wrong answer. The failure mode we design against is a confident wrong answer that nobody checked. We design against it rather than just warning about it.
What does it cost?
Design is a flat $3,000. That covers the financial analysis, the intake audit, and the full system design, and the design is yours to keep and use whether or not you build with us.
Builds typically fall between $5,000 and $50,000. Treat that as a range and nothing more. It is not a floor, not a ceiling, and no engagement is priced off it. Your number is calculated from the savings your own analysis documents, and it can land outside that range in either direction.
Our fee is 15 percent of the documented savings and your firm keeps 85 percent. Savings figures are estimates produced by the analysis, not a guarantee of results. No charge per person and no charge per use. Monthly support after launch is recommended but not contractually binding. No multi-year contract.
The number depends on how many workflows we are building, how much of your existing material we can use as-is, what it has to connect to, and how much training you need. We give you the figure after we have looked at your actual work, not before.
If it is out of range for your firm, we will tell you in the first conversation rather than after you have spent time on it.
What happens when the project ends? Am I stuck with you?
No. Once the build is paid for, the system, the documentation, and the training materials stay with your firm for its own use. It is built to run without us and your team is trained to run it.
Keeping us on monthly is a choice, not a requirement. Firms usually do it because their work changes and they want the system to keep up, not because they cannot operate it.
Do I need an IT department?
No. Most firms we would work with do not have one. We build around the tools you already use and we train the people who will actually operate it. If you have an IT provider, we will work with them.
How long before I see anything?
Two to four weeks to understand your work and give you a plan. Four to eight weeks to build, depending on scope. The typical plan has something working within three months of the first conversation. Your written plan states the actual timeline.
What if my team hates it?
That is the most common way these projects fail, and it usually happens because a tool got dropped on people who were not consulted. We start by sitting with the people doing the job, which is partly to design the right thing and partly so it is not a surprise when it arrives.
If your team will not use it, it does not matter how good it is. We would rather find that out in week one.
Why should I believe you? You are a new firm.
SageLogic is new. I am not.
I bring fifteen years of environmental consulting experience, so I know operational headaches firsthand. I spent more than a decade managing projects, writing reports, and working through regulatory demands. I have used AI tools since they became broadly available, and I have built my working practices around security, governance, and data integrity. I do not build theoretical solutions. I build systems to solve problems I have lived through.
Here's what I would ask a firm in my position, and what you should ask me: make me explain exactly what you are building before I pay for the build. Make me tell you what it will not do. Make me put the fixed price in writing. Make me show you the rules before you approve them. Every one of those is built into how we work, and you can hold me to all of them.
My industry is not on your list. Does that matter?
Less than you would think. The pattern is nearly always the same: repetitive documents, knowledge stuck in a few heads, and a mistake that costs real money. If that describes your firm, the industry matters mostly for the vocabulary and the rules, both of which we learn in the first stage.
If your work is highly specialized and regulated in a way we cannot learn quickly enough, we will tell you.
Which AI is this? Do I have to use ChatGPT?
We pick the tool to fit the job and we tell you what we are using and why. You are not buying a subscription to a brand name. You are buying a customized system built around your work, and the underlying tool can be changed later without rebuilding everything.