Pricing
Start with the problem you need to solve.
LUMAREF deployments vary based on the technical content you have, the experiences you want to create, and the systems you need to connect. Most teams start with a focused product family, manual set, or use case — then expand the same connected knowledge over time.
No generic software tiers. No need to scope your entire technical content estate before getting started.
How pricing works
Pricing based on what you are building — not an arbitrary PDF limit.
LUMAREF is more than a document-processing utility. The platform transforms technical content into a reusable knowledge foundation. Pricing reflects the scope of that deployment.
Your technical content
The manuals, parts catalogs, diagrams, product information, and product families you want to bring into LUMAREF.
The experiences you need
Interactive guides, diagram catalogs, AI assistance, parts discovery, internal knowledge, or other customer and team experiences.
The systems you want to connect
Product catalogs, storefronts, websites, dealer portals, internal applications, APIs, and other business systems.
The scale of the deployment
Audience, usage, brands, workspaces, governance, support, and other operational requirements.
We will help you define the smallest useful starting point before discussing a broader rollout.
Common starting points
You do not need to transform everything at once.
The best first deployment is usually focused enough to move quickly and important enough to prove real value.
Prove the experience with real content.
Start with one manual set, product family, diagram collection, or clearly defined business problem.
A focused pilot can help you evaluate
- How well your existing technical content can be structured
- How models, diagrams, parts, and products can be connected
- What the review and curation workflow looks like
- How the finished experience could work for customers or teams
- Where LUMAREF can create the most value next
Good for teams exploring LUMAREF for the first time or evaluating a specific use case.
Discuss a pilot →Put connected technical knowledge to work.
Move from a focused starting point into a production experience for customers, dealers, service teams, parts operations, or other users.
A production deployment may include
- Ongoing technical content processing
- Human review and curation workflows
- Interactive technical guides
- Diagram and parts experiences
- AI search with cited sources
- Product and catalog connections
- Hosted or embedded experiences
- Analytics and usage insight
Good for teams ready to launch a meaningful customer-facing or internal experience.
Talk through your deployment →Expand across products, audiences, and systems.
Use the same technical knowledge foundation across multiple product families, brands, business units, or destinations.
Enterprise deployments may include
- Larger and more complex technical content estates
- Multiple brands or workspaces
- Public and internal knowledge experiences
- Custom integrations
- APIs and embedded delivery
- Advanced governance and access requirements
- Implementation and migration support
- Service-level and commercial requirements
Good for manufacturers treating technical product knowledge as shared infrastructure across the aftermarket organization.
Talk with us →A focused starting point
Start where technical knowledge is creating the most friction.
A parts catalog customers cannot navigate
Turn static diagrams and parts tables into an interactive parts-discovery experience.
A dealer network that keeps calling support
Give dealers a better way to find applicable, source-backed technical answers.
A support team searching through PDFs
Connect questions to the relevant model, manual, section, diagram, and evidence.
A storefront disconnected from technical content
Connect diagrams and part references with the products people need to find.
Years of legacy manuals holding back a digital initiative
Modernize existing technical content without rebuilding your documentation operation.
An AI project that needs a verified technical foundation
Build on structured, connected, human-reviewed knowledge — not raw document text.
Start with one problem. Expand the same knowledge into more experiences over time.
Getting started
A useful conversation starts with your content.
You do not need a complete technical-content inventory before talking with us.
-
1
Tell us what you are trying to improve
Customer self-service, dealer enablement, parts discovery, product support, content modernization, or another technical knowledge challenge.
-
2
Show us representative content
A manual, parts catalog, diagram set, product export, or example of the experience that is difficult today.
-
3
Define a focused starting point
We will help identify a scope that is useful enough to prove value without requiring a company-wide transformation project.
-
4
Receive a clear recommendation
We will outline the proposed starting point, what LUMAREF would do, what your team would need to provide, and the expected commercial structure.
Pricing FAQ
Common questions about how LUMAREF pricing works.
Why does LUMAREF not publish fixed software tiers?
The complexity and value of technical product knowledge varies significantly between manufacturers. One company may want to modernize a single illustrated parts catalog. Another may want to connect thousands of technical references with its product catalog and deliver the result across customer, dealer, and internal experiences. We would rather scope the smallest useful deployment than force every company into an arbitrary document or part-number limit.
What determines the price?
Pricing generally depends on the scope and complexity of the technical content, the number of product families or knowledge domains involved, the experiences being deployed, product and catalog connections, usage and audience requirements, and implementation and support needs. We will explain which factors matter for your specific use case before you make a commitment.
Can we start small?
Yes — and that is usually the best way to begin. Many teams start with one product family, one collection of manuals, one parts catalog, or one high-value customer experience. The same structured knowledge can then expand into additional use cases over time.
Can you give us a budgetary estimate before a full project?
Yes. After a short conversation and review of representative content, we can provide a recommended starting scope and commercial range. You do not need to complete a lengthy implementation process just to understand whether LUMAREF is a realistic fit.
Is pricing based on the number of users?
Not by itself. The value of LUMAREF comes from the technical knowledge being structured, connected, and put to work. Audience size and usage may matter at scale, but seat count alone does not describe the value of the platform.
Is pricing based on the number of PDFs or AI conversations?
Not as the primary measure of value. Document volume and usage can affect the technical scope of a deployment, but LUMAREF is not designed as a pay-per-PDF utility or generic chatbot service. The goal is to create a reusable technical knowledge foundation.
Do we need to replace our current documentation or business systems?
No. LUMAREF is designed to start with the content and systems you already have. It can power complete hosted experiences or connect technical knowledge with websites, storefronts, portals, internal tools, APIs, and other systems.
What happens after a pilot?
That depends on what proves most valuable. You may expand into more manuals or product families, from internal use to customer self-service, from diagrams into parts and product connections, from a hosted experience into your existing website or portal, or across additional audiences, brands, or business systems. The goal of a focused starting point is to learn where connected technical knowledge creates the greatest value before expanding.
You do not need a pricing tier.
Show us the technical content or business problem creating the most friction today. We will help you determine what a focused LUMAREF deployment could look like.