Insurance operations were never meant to be this fragmented.
Disconnected systems create invisible costs.
NewTec connects the operation around the way your business actually works.
One connected path from submission to reporting.
One connected operating environment.
Intelligence where it helps. Human control where it matters.
Your operation. Connected, visible and ready to grow.
Insurance operations were never meant to be this fragmented.
Submission emails, application PDFs, spreadsheets, loss runs, quote requests, broker messages, policy documents, reporting windows, the same work, scattered across disconnected places. Disconnected systems create invisible costs.
NewTec connects the operation around the way your business actually works.
One connected path from submission to reporting, each stage activated, tracked, and visible.
One connected operating environment, with intelligence where it helps and human control where it matters.
Policy administration, underwriting workflows, rating and quoting, issuance, the broker portal, reporting, integrations, and AI-assisted operations, governed by a visible human-review checkpoint. Nothing is rated or bound until your underwriter approves.
Your operation. Connected, visible and ready to grow.
Illustrative interfaces, sample data. Real screens available in a guided walkthrough.
Modernize your MGA in phases, without rip-and-replace.
Broker rating portals, submission-to-issuance workflows, and carrier reporting that work with the systems you already run. Built by people who run MGA systems for a living.
Free, 60–90 minutes. Then run it in production for 30 days, the monthly rate starts after the trial.
Your book is growing. Your systems are a patchwork.
An AMS here, a CRM there, an online rater and third-party dashboards, with email holding it all together. Nothing failed. You outgrew it.
Re-keying between systems
The same submission typed into every system it touches, and every retype is a chance to send a carrier the wrong number.
The month-end reporting scramble
Carrier and management reports assembled by hand from exports, weekends included.
One person who knows how it all works
The workflow lives in someone's head and someone's spreadsheet, and they'd like a vacation.
The good news: there's a path that doesn't start with replacement.
Put a number on what the patchwork costs The re-keying cost calculator, a few honest inputs, your own math.Stop outsourcing your operations.
The back-office work you send out comes back re-keyed, delayed, and disconnected from your system of record. It does not have to. The AI Operational Workforce does that intake and preparation in-house, on your own core.
Today, outsourced
Work leaves the building.
- Submissions, data entry and reporting handed to vendors and outside teams
- Re-keyed into your systems on return
- Knowledge and control sit outside your walls
With NTIS, in-house
Work stays on your core.
- The AI Operational Workforce prepares it; your team approves it
- Structured on your system of record, so nothing is re-keyed
- A named person decides, so control stays inside
The vendor you are already paying is the line item this replaces. Start a 30-day trial on that workflow.
Which of these is happening right now?
Nobody modernizes for fun. Something is forcing the issue, so start there, not with a platform tour. Pick the one that sounds like your week.
A new program has a launch date
The carrier set the date, and your current stack is hard-coded to program #1. You need a second program stood up without rebuilding the first.
See the submission-to-issuance build →Your carrier tightened the reporting
New bordereaux formats, data specs, or a security posture, and the capacity relationship depends on getting month-end right, on their schedule.
See the carrier-reporting hub →Producers are drifting to faster quotes
Submissions leak to whoever can quote first. A broker portal your producers actually use closes the gap without adding intake staff.
See the broker portal build →A re-keying error reached a carrier
The cost of the patchwork finally became visible. Connecting your AMS, rater, and carrier feeds ends the retype that caused it, without a rip-and-replace.
See how we connect what you have →Not sure which one you are, or it's more than one? That is exactly what the free mapping session is for. Bring us your messiest workflow →
And if none of them is you, we would rather say so early: we publish who we build for, and who we turn away. It is a short list, and it is honest.
We get shit done.
Scope
Tell us your vision and goals, set expectations.
Build
Development begins with utilization of the latest available technologies.
Deploy · GTM · Go-live
It goes into production and you operate it for 30 days with real submissions.
Upgrade
Production deployment doesn’t end here, we continuously upgrade infrastructure to keep current with the latest technologies.
Migration rule: renewals are never cut over until validation passes.
Built inside a working MGA, and still running one.
These patterns weren't invented for a pitch deck. A broker rating portal in production. Submission-to-issuance workflows in daily use. Reporting that carriers actually receive. The same senior team designs, builds, and runs them.
- A working system, in production, for 30 days. We stand it up on your own workflow and you run it on real submissions. The monthly rate starts after the trial.
- iO, our execution agent, quote-and-submit in conversation, human-approved, in production since August 2026. See how the iO intelligence layer works.
- Ask for the guided walkthrough, real screens, real workflows, shown live in your mapping session.
What we build (and run) for you.
Three core builds, each provable in a working MGA. Pick the one your trigger demands; the rest can wait until they've earned their place.
Broker rating portal
Self-serve quoting connected to your rating and issuance, the portal your producers actually use.
Explore the broker portal →Submission-to-issuance workflow
One tracked flow from submission to rate, quote, bind, and issue, with your team approving every step that matters.
Explore the workflow →Carrier & management reporting
The bordereaux and reports your carrier partners demand, on schedule, without the spreadsheet assembly line.
Explore carrier reporting →Integrations & data migration
Connections to the AMS, rater, and carrier workflows you already have, and migration with a validation report.
Explore integrations & migration →AI Operational Workforce
The mundane, repeated work (reading submissions, proposing Classifications, matching and assembly) runs as automated work with feedback loops. A person approves anything that touches rating or binding, documented for your carrier's reviewer.
Explore governed AI →Hosting & support
We run what we build, monitored hosting, written support norms, and a named senior lead who knows your systems.
How it works →Not a chatbot. Not a copilot. A workforce.
Three coordinated assists run on one core, reading the work, holding your rules, and preparing the action, while a named person approves anything that touches rating or binding.
Lina · Intake
The reader. It takes the submission as it arrives, attachments and all, and structures it onto the record.
Yasha · Knowledge
The brain. It holds your rules and your appetite, and reasons over what the file actually says.
iO · Execution
The doer. It prepares the action, proposes Classifications with ranked alternates, and logs every step for your carrier's reviewer.
One workforce, three roles, all on the same core and all logged. Meet the workforce.
We connect before we replace.
"Our data is a mess" isn't a disqualifier. It's the starting condition we design for.
- Your AMS stays Keeps running, until something better has earned its place; Phase 1 connects to it, not around it.
- Carrier connections Keeps running, the workflows your capacity partners rely on don't blink.
- Data migrates with a validation report, and renewals are never cut over until it passes.
- No big-bang go-live. Ever.
These aren't sample numbers. They're the standing rules of every migration we run, and you get the validation report either way.
A person approves anything that touches rating or binding.
Our AI speeds intake and classification. It does not rate, bind, or file on its own, and every suggestion is logged, so your carrier's reviewer can see exactly how it works. iO, our execution agent, runs through this same checkpoint: it prepares the whole quote file, and a named underwriter approves anything that touches rating or binding.
Intake
The AI reads the submission and extracts what matters.
Triage
Classifications and data proposed, ranked, reasoned, and logged.
Human approves
Your underwriter decides. Nothing proceeds without them.
Record
The full trail (suggestion, decision, outcome) kept for audit.
Written for the regulatory environment your carriers are watching: documented AI use, human-in-the-loop controls, reviewable logs, aligned with the NAIC model bulletin on AI use, adopted by 24 states and the District of Columbia as of July 2026.
Honest about the lift.
Nobody's team has spare capacity during renewal season. The plan is built around that.
The build, the data, the plumbing
Requirements, build, integrations, migration, validation, hosting, and the go-live checklist, run by a named senior lead who also runs production MGA systems, not a rotating bench.
About 3–5 focused hours a week
From the people who know your workflows, to confirm how things actually work, review what we build against reality, and approve each gate. That's the whole ask.
We take on a small number of new implementations at a time.
Every engagement is led by senior people, and we publish real phase durations from real delivery history rather than a universal promise. Your Assessment includes a dated plan for your specific scope. We'd rather tell you our true capacity than miss your go-live.
Don't take the website's word for it.
We'd rather put a working system in your hands than show you badges.
A roadmap, a demo, or a press release
Ask any vendor one question: what is the production date, and who is running it today on real business? An announcement is not an answer.
Running on real operational work
iO has been in production since August 3, 2026, on our own core, with a person approving anything that rates or binds.
Run it for 30 days first
We stand up a working system on your own workflow, not a demo, not a sandbox. You operate it in production for 30 days, on real submissions. The monthly rate starts after the trial.
Start the 30-day trial →See the systems running
A guided walkthrough of the live portal, workflow, and reporting screens, real systems, shown to you in your mapping session.
Book a walkthrough →Read who we turn away
We publish who this is for and who it isn't, including the engagements we decline. Judge us by what we won't claim.
Who we’re not for →We do not publish named case studies yet. Until we can, the evidence is a walkthrough on your own submission and a trial you run yourself, in production, for 30 days.
A small, senior team, on purpose.
NTIS is insurance people who build systems: a career that runs from personal lines in the 1990s through commercial E&S point-of-sale systems in the 2000s to designing and running a working MGA's stack today. You'll know exactly who is on your engagement, because it's the same people who answer when something matters.
- A named senior lead on every engagement
- Support norms and response expectations in your agreement, not in a brochure
- Monitored hosting for everything we run
- Your data is yours, exportable, documented, never hostage
Built for growing small MGAs, and honest about who we're not for.
This is probably you if…
The profile where our pattern is proven.
- You're roughly $10M–$50M GWP with 8–30 people and 1–3 programs, one of them scaling or launching
- Your stack is an AMS plus spreadsheets plus carrier portals, held together by re-keying
- Something external is forcing the issue, carrier reporting demands, a program launch date, or producers drifting to faster-quoting competitors
- The founder or COO can make this decision, and wants fixed scope, not an open-ended project
We'll say so if…
Engagements we decline or redirect, told to you up front.
- You're running a formal enterprise-core RFP with procurement scoring. We'll lose on paper depth and we'd rather not waste your cycles
- You need a big-bang rip-and-replace on a fixed date less than 90 days out
- You expect your vendor to own regulatory filings or compliance responsibility. That stays with you, and anyone who says otherwise is selling
- Your security review requires a SOC 2 Type 2. We hold a SOC 1 Type 1, and our security page states the difference plainly, so you’ll know in five minutes
Questions founders actually ask.
Bring your messiest workflow.
A 60–90 minute working session: we whiteboard your intake-to-issuance flow, put numbers on the three costliest frictions, and hand you the one-page map, same day, yours to keep. No deck, no pressure.
- The map is yours to keep, whether or not you ever hire us.
- Phase 1 runs alongside your current process. Your renewals are never the test environment.
- You operate the system in production for 30 days on real submissions, the monthly rate starts after the trial.
- Stop at any phase boundary and keep everything you've paid for, no bundle, no lock-in.
- Your data is yours, exportable, documented, with exit terms in writing.
No deck, no pressure, and the map is yours to keep either way.