You own the code. The fee is fixed.
The two questions every buyer asks before anything else, answered where you can hold us to them: what it costs, and what stays yours.
Two questions every buyer asks first, answered in writing
Before anyone asks what we build, they ask two things: what will it cost, and what happens if we part ways. Both deserve a straight answer on the website, not on a call.
Every WiscAI engagement is a fixed fee, quoted before it starts. Every system we build is yours: the source code, the written rules, the data, running in your own cloud accounts. If we stopped working together tomorrow, you would keep everything and it would keep running.
That is not a special arrangement. It is the only way we work, and this page spells out what it means so you can hold us to it.
What "you own the code" means here
The source code is yours. Not a license to use it. Ownership, stated plainly before you sign, so a future disagreement with your builder is a business inconvenience rather than an operational emergency.
It runs in your accounts. Your cloud, your keys, your off switch. If a system can only run on the builder's infrastructure, you bought a product with extra steps.
No per-seat license on custom work. Add users, add departments, add a second plant. The system does not get more expensive because more of your people use it.
The written rules are yours too. When a build captures how your experts do the work, those rules are documented in plain language inside your systems, where your team can read and change them. How that works →
The assessment map is yours whether or not you build with us. Every opportunity we find, written up with the time at stake and what it would take, belongs to you at the end of the three weeks.
What "fixed fee" means here
The number is quoted before the work starts, and it does not move as the work goes on. A change in scope is a new number, agreed first.
| Engagement | Length | Fee | What you keep |
|---|---|---|---|
| AI opportunity assessment | 3 weeks | $10K to $25K, fixed | The scored map, the write-ups, a build quote. No commitment past this. |
| Build | Scoped from the assessment | $25K to $150K+, fixed | The system, the code, the documentation, running in your accounts. |
| Coaching your team | 1-week diagnostic, 2 to 4 week pilot, then monthly | Fixed per phase | The skills, in-house. Your people do the work. |
| Training your staff | Scoped to the team | Fixed; up to 80% reimbursed by WisTRAIN for Wisconsin employers | Trained people and the training plan. |
| The first conversation | 30 minutes | Free | A straight answer on whether it is a fit. |
Build fees are sized to the work: a contained workflow ships in weeks; a complex system gets the time it needs. Both are quoted from the assessment, not guessed on the call.
What it looks like on real engagements
A Wisconsin credit union hired us to score its consumer lending and retail workflows and turn the results into a build roadmap. The roadmap is theirs when it is done; leadership can act on it with us or without us.
A national catalog retailer runs a campaign studio we built hands-on with its marketing team, against its own brand book, with its brand-voice and compliance rules enforced in code. It is in daily use by the retailer's team, in the retailer's accounts.
A Wisconsin commercial printer has four AI projects running, from invoice generation to production intelligence. The billing rules the system learned are written down where the company can read them.
More on each is on the work page. Names are withheld; specifics are shared with permission.
Five questions to ask any AI builder, including us
Who owns the code, in writing? If the answer takes more than a sentence, it is a license.
Where does it run? Your accounts, or theirs. Ask what happens on the day you stop paying.
Is accuracy proven on our data before we sign? Any builder confident in their approach will test on a real sample of your documents and show you the number, including the cases it gets wrong.
Is the handover scoped as work? Documentation, monitoring, and time with your team, written into the engagement. A handover that is not scoped does not happen.
Does the team that scoped it ship it? Re-briefing a second team is where context, and money, go missing. Ours does not hand off. And if a product would serve you better than a build, we will tell you →
The ones that come up next
Do you keep any rights to reuse what you build for us?
The code we write for you is yours. We state the ownership terms plainly before you sign, so there is nothing to interpret later, and there is no per-seat license on custom work.
What if we stop after the assessment?
Then you stop, and you keep everything the assessment produced: the scored map, the write-up of each opportunity, and the build quote. Some clients hand it to their own team, some take it to another vendor, most continue with us. There is no commitment past the assessment itself.
What happens if the scope grows during a build?
The number does not move on its own. If you want something added, it is quoted as a change and agreed before the work continues. A fixed fee protects you from surprise bills and protects us from an engagement that never ends, which is why we scope carefully before we quote.
Where does the system run?
In your cloud accounts, with your keys and your off switch. If you run on AWS, you can also engage us through AWS Marketplace, where our implementation services are listed. Nothing we build for you depends on our servers to keep working.
Who maintains it after the handover?
Your team, once the handover is done, and the handover is scoped as work rather than promised at the end: documentation, monitoring, and time with the people who will run it. If you want us close by afterward, monthly advisory is a light retainer, not a dependency.
Is the 30-minute call really free?
Yes. It is a conversation about whether the problem is a fit for AI and for us. If it is not, we say so on the call.
- Featured by Apple in Best New Apps & Updates (LilSense)
- Serving collegiate and professional programs, including an NCAA national championship team
- Founded Wisconsin's longest-running AI practitioner community (meeting weekly since 2024)
- Co-hosts the AI Leadership Breakfast Forum with Steve Cretney (EVP, Colony Brands)
Want the number before the call?
Tell us the workflow and the size of the team, and we will tell you which engagement fits and what it costs. 30 minutes, no pitch.
Book a Call