Planara Conduit
Technical
Service
Intelligence.
Planara Conduit turns manufacturer manuals, standards, and service bulletins into cited, safety-validated answers for the people who service the equipment.
What oil does the F300 require?
Specifications
Run engine to operating temperature before draining. Hot oil flows more completely. Use caution — surfaces will be hot.
The Problem
25% of service costs are failed first visits. The knowledge to fix it is trapped in manuals nobody reads and techs who are retiring.
of service costs are failed visits
A failed first visit adds 2 more truck rolls and 14 days to resolution. Bottom performers waste 44% of service spend on repeat visits.
Aquant Field Service Benchmark, 2026
first-time fix gap between top and bottom
Top companies fix it right 88% of the time. Bottom performers: 60%. The difference is knowledge — who has it, how fast they can find it.
Aquant Field Service Benchmark, 2026
of service orgs face disruption from retirements
When a senior tech retires, years of undocumented fixes walk out the door. No manual captures what actually works in the field.
The Service Council
What Conduit is
Manuals, standards, and bulletins, in.
Cited, safety-validated answers, out.
Conduit ingests the authoritative documentation a manufacturer already owns — manuals, standards, service bulletins — and resolves every question against a retrieved page. Every answer is sourced. Every warning is preserved. The next technician gets a better answer than the last one got.
Three outcomes
Three audiences. One platform.
The same Conduit deployment serves the technician on the bench, the owner at the dock, and the product team back at HQ — each with the surface that fits how they actually work.
What oil does the F300 require?
Field technicians
Cited answers in seconds, not search trips.
Specs, parts, procedures — pulled from your manuals, not invented. Every answer cites the page. Safety warnings come through verbatim.
What oil does the F300 require? · 7.1 L YAMALUBE 4-M FC-W · cited
Try the technician demoNewport Marine
Your certified dealer
Reel Therapy
2023 Grady-White Canyon 326
Dealer service operations
Owner questions become service revenue.
A dealer-branded surface answers owner questions in plain language and routes the relevant conversation back to the dealership for booking, parts, or follow-up.
When is my next service due? · 153 hrs to next interval · book
Try the owner demoTop unanswered questions
OEM product teams
See what your fleet is actually experiencing.
Failure patterns, documentation gaps, recurring questions — by model, by region. The questions Conduit can't answer are the documentation you need to write.
Top 10 unanswered questions · F300 · last 30 days
Backoffice surfaceNot another chatbot
Generic AI vs. Technical Service Intelligence
Same question. Radically different output.
Illustrative example. Generic AI responses vary; the comparison shows the structural difference, not a benchmarked head-to-head.
Specifications
Run engine to operating temperature before draining oil. Hot oil flows more completely. Use caution — oil and surfaces will be hot.
Full context, not general knowledge.
Conduit queries your actual documentation library — manuals, standards, service bulletins. When telemetry is connected, it's cross-referenced into the answer. Generic AI draws from public training data.
Your IP stays yours.
Private isolated pipeline. No training on your data. No sharing across customers.
What makes Conduit different
Built for the field, not for the lab.
One library, every dealer
Conduit deploys at the OEM. Their dealer network — every dealer, every technician — answers from the same library. The manufacturer writes the manual once. Everyone downstream answers consistently.
Corrections improve the next answer
Every correction a technician submits reviews, validates, and improves the next answer for the next technician — inside the same tenant. The platform learns from real repairs, not from a lab.
Cited or it doesn't ship
Every spec, every torque value, every step is sourced from a retrieved page. If the manual doesn't say it, Conduit doesn't either. Citations are tappable to the original page image, and confidence is scored on every answer.
See what your dealers are actually asking
What questions are dealers asking? Which procedures are taking longest? Where do answers fail? Conduit surfaces the patterns across the OEM's own dealer network — and the documentation gaps the OEM can finally close.
Verticals
One platform. Configured per vertical.
Marine is our reference deployment. The other four are open to early pilots — your documentation, your terminology, your standards, on your timeline.
Marine
Outboard, sterndrive, and diesel propulsion. ABYC standards. Dealer-network distribution.
Manufacturing
Production line uptime, OSHA 1910, lockout-tagout, shift-handoff knowledge loss.
HVAC
EPA 608, ASHRAE, ASE. Dispatch-based field workforces, commercial and residential.
Heavy & agricultural equipment
Hours-based service intervals, multi-engine vehicles, dealer-network OEMs.
Power generation
Genset maintenance, runtime-based intervals, distributed service networks.
Proof
Conduit is early. The team is not.
We've shipped products used by billions before. Now we're applying that experience to equipment service. Currently in active conversations with marine OEMs and a global manufacturing operator.
1B+
Users reached by products this team has shipped
25+
Fortune 100 clients across prior engagements
Multiple
Successful exits
Team experience includes
Ford · Airbus · Google · Apple · Uber · Disney · Goldman Sachs · Samsung
How we engage
Prototype
1–2 weeksWorking prototype from your documentation. Ingest 2–3 manuals, configure one use case, demo with your data.
Pilot
4–8 weeksProduction deployment with real users. Full library, telemetry where available, measured outcomes.
Platform
OngoingPer-tenant SaaS. Multi-model support, dealer-branded surfaces, continuous improvement from technician corrections.
Deep dive — aftermarket economics
A separate piece of long-form on a specific question: why aftermarket service is where the manufacturing margin actually lives, and the documentation gap that's keeping OEMs from capturing it. Optional reading — not the foundation of the product.
Get started
Working prototype in 1–2 weeks.
We build a Conduit deployment from your actual equipment documentation so you can see the answer quality before committing anything. We need three things:
2-3 equipment manuals
Owner's manual, service manual, or technical bulletins. PDF is fine.
One use case
Service operations, dealer support, owner self-service — pick the one that matters most.
One point of contact
Someone who knows the product and can validate results. 30 minutes a week.
Common questions
What buyers ask us.
Generic AI assistants are built for general knowledge work — summaries, drafts, open-ended questions. Equipment service requires structured, safety-critical output: spec tables, procedural steps with mandatory sequences, parts lists with real SKUs, and verifiable citations to specific manual pages. A wrong answer about lubrication specs means a seized engine, not a bad email. Conduit is built for that context.
Knowledge bases require users to know what to search for. Conduit understands the question in context — cross-referencing documentation with available service history, equipment configuration, and (where connected) live telemetry. Ask "why is my engine overheating?" and get a diagnostic procedure that takes your equipment into account, not a generic article.
Your documentation stays yours. Conduit processes documents through a private, isolated pipeline. No training on your data, no sharing across tenants, no third-party access. Each manufacturer's knowledge base is fully separate.
A working prototype from 2–3 manuals takes 1–2 weeks. You'll see your own documentation returning structured, citation-backed answers before committing any budget. The pilot phase (4–8 weeks) layers in telemetry where available, surface integrations, and real user testing.