Staff
Move messaging, approvals, leave and issues onto the new systems on your servers and use them for real work.
Install the systems, get your people using them, and let AI handle development
A six-month process that changes how your company works with AI: three months to install it on your own servers, three months to make it stick.
Talk to us
Why AI rollouts stall
MVPIT solves all three at once. You don't need one vendor to install, another to train and a third to fix.
- 1Data is scattered across outside tools, so AI has nowhere to work
- 2Staff can't use the new systems or AI
- 3Nobody is left to fix things after rollout
MVPIT solves all three at once. You don't need one vendor to install, another to train and a third to fix.
Six stages: what we do, what you do, what you get
| Stage | What we do | What you do | What you get |
|---|---|---|---|
| 01SurveyMonth 1 | What we doMap where your tools, workflows and data live | What you doShare the org chart, approval forms and the list of tools in use | What you getStatus report |
| 02DesignMonth 1 | What we doDecide what to replace and what to connect by API, and send server specs for each product | What you doPrepare servers, grant database access and name the people in charge | What you getTransition plan and server requirements |
| 03InstallMonths 1–3 | What we doInstall on your servers, set up your organization, move forms and history over, and put everyone on one login through your own identity server | What you doHand over messenger channel accounts and keep using your old tools alongside the new ones | What you getSystems running on your servers |
| 04AdoptMonths 2–3 | What we doTrain staff, agents and developers; build the support knowledge base and run safety tests | What you doReview the support knowledge; agents use old and new side by side | What you getCompleted training and verified answer cards |
| 05AI developmentMonths 1–6 | What we doFrom month 1, QAbox opens as the request desk. File a request and AI reviews and fixes it. The person who filed it checks the fix and sends it back with a reason if it isn't solvedDocuments too: AI fills in government forms (DocBox) Try it ↗ | What you doJust file what to fix or add | What you getQAbox request desk and document AI (DocBox) |
| 06SettleMonths 4–6 | What we doAcceptance review in month 3, source code handover, defect fixes, then operations handover and advice | What you doSign off in month 3 and decide when to cancel your old tools | What you getQuarterly report, team contribution report (resolved, value grade, quality), and a proposal for the next three months |
The first three months
What slows things down isn't development, it's waiting on things from you. So we ask for those first and install everything else while we wait.
| Month | MVPIT | Customer |
|---|---|---|
| Month 1 | MVPITWe start installing and request servers, the org chart and DB access. QAbox opens as the request desk, forms move over, you start using the new tools alongside the old ones, and the knowledge pipeline is switched on | CustomerPrepare servers, the org chart and forms, grant DB access and name a contact. Hand over channel accounts too |
| Month 2 | MVPITWe migrate history, connect channels, build the support knowledge and run safety tests | CustomerReview the knowledge we built and send feedback |
| Month 3 | MVPITWe run side by side with your old tools, open the KPI dashboard, and give you the data to decide on retiring old tools along with first-response automation measurements | CustomerAgents use it alongside, and you sign off at the month-3 acceptance review |
If something we need from you is late, only that product's schedule slips; the others keep going.
Training is stage four, not a separate product
Support agents
Handle every channel in one console, check AI answers that come with evidence and sources, and take over the questions AI passes on.
Developers
A one-day, eight-hour hands-on workshop. Using one of your real specs, take it from planning to release with AI.
- 1Tool setup
- 2Planning
- 3Environment
- 4Design
- 5Build & infra
- 6Debug & verify
- 7Release
AI does the work; people make the calls and check it.
Planning & admin
Write grant forms and reports in DocBox. Practice setting up the file drawer and company profile, automatic drafting, and editing by command.
One contract, two decisions
- 01One contract, two decisions. At the month-3 acceptance review you decide on the next three months
- 02Same amount billed on the same day each month, with a monthly report
- 03No monthly operating fee
- 04Source code handed over after month-3 acceptance
- 05Existing services stay on and connect by API
- 06Data never leaves your servers
- 07One login through your own identity server
We'll quote a price once we've seen the scope in consultation.
Before and after
KS24
Immigration services · since 2026.06- Before
- An old Oracle system, with documents on a NAS. Staff typed document details into screens by hand and did settlements in spreadsheets pulled from the database.
- Done
- Rebuilt the customer site and admin console and moved the old Oracle data into PostgreSQL: 138 live tables, zero orphaned records, payment totals matched, 894 NAS documents recovered, and server costs down about 60%.
- After
- 14 languages and 78 console screens. 1,161 ID documents read automatically, 26 government forms generated automatically with e-signatures, a visa points calculator, and consultations, cases and payments on one screen (the workbench).
Mobile carrier (MVNO)
ACE · AI support- Before
- Agents looked up material and wrote every answer by hand.
- Done
- AI answers never go straight to customers; agents review, edit and send them. Questions with no evidence, policy questions, account lookups and outages go to an agent, and the agents' edits feed the AI the next day. 23,943 past chats were turned into 661 answer cards.
- After
- Usable drafts rose from 30% to 70%, questions AI couldn't help with fell from 70% to 17%, half of responses came within 3.5s, and there were 0 real safety violations (all 3,520 sources were the company's own)
Frequently asked
Who prepares the servers?
Your company does. MVPIT sends a server spec request per product in month 1 and does the installation and setup.
Does it work on a closed network?
ACE and MultiTalk can be installed on a closed network. We decide the rest of the setup together in consultation.
Do we have to drop our current messenger and approval tools right away?
No. You run them alongside the new systems and decide whether to cancel at the month-3 acceptance meeting.
What if we have no development team?
That works. File what needs fixing in QAbox and AI reviews and fixes it. After month 3 we hand over operations and keep advising.
Do you train AI on our data?
No. ACE does not train a model; it finds evidence in your company's material, answers with sources, and hands over to a person when there is no evidence.
Can we run it ourselves afterwards?
Yes. Source code is handed over after month-3 acceptance, and over the next three months we hand over the operations manual and deploy, backup and recovery procedures, with operations advice.
How do we know developers really did the work?
QAbox reports on contribution. One unit is one issue that was resolved and stayed closed, and we look at it three ways: outcome (resolved), value grade, and quality (send-backs and reverts). No single number decides, and there are no leaderboards for lines of code or commits. We don't collect screens, keystrokes or login time. It starts as a team report; individual scorecards are something the company can choose to turn on. The system suggests a value grade and a person confirms it. Developers see the evidence on the same screen and can object. Using AI never counts against anyone. In one month AI fixed 243 issues, and half of them were deployed within 12 minutes of being filed.
Can Korean HWP document work be done with AI too?
Yes. DocBox is AI inside a Korean HWP/HWPX editor: it drafts documents from your files and company profile, edits on a one-line command, and adds tables, charts and diagrams. Files stay on the device, AI receives only the relevant parts, and on-prem uses your own AI key. If you have a Claude subscription, you can connect your own Claude and use it without the trial limit (our server only relays and stores no documents). Try it ↗
Talk to us
Tell us your headcount and the tools you use now, and we will reply with what the discovery stage will look at.
hello@mvpit.dev