Questions, answered

A customer portal starts with mapping what your customers actually do with you — orders, documents, support requests, account changes — and which systems hold that data today. We design the information architecture and workflows first, then build the portal as a custom web application connected to your ERP, CRM or order system through an integration layer. Authentication uses single sign-on with role-based access, so dealers, direct customers and internal staff each see the right view. The build is staged: a working core (login, orders, documents) ships first, then support workflows and self-service features are added in increments. Typical engagements run several months depending on integration depth, and the portal remains yours — no per-seat platform licensing.

Portal development is the design and build of a secure, login-based web interface where a defined group — customers, partners, dealers or employees — can work with your company's data and processes in self-service. Unlike a marketing website, a portal is transactional: users place orders, download documents, track projects, register leads or manage their accounts. Development covers information architecture, user experience design, the application itself, and integration with the systems that own the underlying data, such as an ERP or CRM. The distinction from off-the-shelf portal software is that a developed portal is shaped around your specific product logic and workflows rather than forcing your processes into a template.

Off-the-shelf client portal software is the right answer when your workflows are standard: shared files, messages, invoices. It stops being the right answer when your portal has to reflect real product complexity — configured products, contract pricing, multi-level dealer hierarchies, or deep ERP integration. Platforms constrain you to their data model and charge per seat as you scale. A custom portal costs more upfront but is built around your actual processes, integrates with the systems you already run, and carries no licensing that grows with your customer count. A practical test: if you are maintaining spreadsheets alongside a portal tool to cover what it cannot do, you have outgrown it.

A customer portal sits between your customers and your internal systems. The customer signs in through a secure login, and the portal shows them a personalized view assembled in real time from your business systems: their orders from the ERP, their documents from your file store, their support tickets from your helpdesk. When they act — reorder, approve a quote, upload a file — the portal writes back to those systems through controlled integrations, so your team keeps working in the tools they already know. Permissions decide who sees what: a dealer sees dealer pricing, a direct customer sees list pricing. Done well, the portal removes the email-and-attachment loop that otherwise consumes your customer-facing staff.

A 3D product configurator is an interactive tool that lets a buyer assemble their version of your product visually — choosing dimensions, materials, colors and options — while the tool renders the result in real time and keeps every combination valid. Behind the visual layer sits a rules engine: it knows which options exclude each other, how each choice affects price, and what the resulting bill of materials is. Configurators are standard practice for furniture, industrial equipment, building products and vehicles, where the number of valid combinations is too large for a static catalog. The output is a priced, buildable specification that can flow directly into your quoting or order system.

SaaS configurator platforms are built for the common case: visual options, standard pricing, e-commerce checkout. They run out of road when your product logic is genuinely complex — engineering constraints between options, pricing that depends on contracts or regions, output that must generate a manufacturable BOM, or integration into an ERP your business runs on. At that point teams start maintaining workarounds outside the platform, which is the signal to build. A custom configurator embeds your real product rules, integrates with your actual systems, and presents it in an interface designed for your brand and your buyers rather than a template shared with every other platform customer.

Custom configurator projects here typically run from $50,000 for a rules-based configurator with quote output, up to $200,000 and beyond for full 3D configuration with real-time rendering, complex constraint logic and deep ERP/CPQ integration. The main cost drivers are the complexity of the product rules, whether 3D assets exist or must be produced, and how many systems the configurator must read from and write to. We scope in tiers so the first release ships a working core — the highest-value product lines with essential rules — and later phases extend coverage. Every engagement starts with a mapping session that produces a fixed scope and price before build begins.

A knowledge base is structured around the questions users actually bring, not around your org chart. We start from support ticket data and search logs to find the real question inventory, then group it into task-based categories — getting started, configuration, troubleshooting, billing — with one canonical article per question. Each article follows a consistent template: the answer first, then steps, then edge cases. Navigation offers two routes to everything: browse by category and search with synonyms mapped to your customers' vocabulary. A good structure is measured, not assumed — article views, search terms that return nothing, and ticket deflection tell you where the structure is failing and what to write next.

A knowledge base is a searchable, self-service library of answers about your product: how to set it up, how to use each feature, what to do when something fails. A familiar example is the help center behind any major software product — categorized articles, a search bar, step-by-step guides with screenshots. For manufacturers the same pattern covers installation guides, maintenance schedules, spec sheets and troubleshooting trees. The business case is ticket deflection: every question answered by an article is a question your support team does not handle manually. For complex products, a well-designed knowledge base also feeds AI assistants and search engines, which increasingly answer your customers' questions whether you provide the source material or not.

Japanese quotes use person-month (人月) units; fixed-price per-feature quoting is the alternative we favor for defined scopes.

Product Systems is a design and engineering studio, and every configurator, portal and internal tool we deliver is custom-built around one client's product logic and systems. You own the code and the roadmap; there is no per-seat subscription and no platform template. Teams typically come to us after evaluating configurator platforms and finding their product rules, pricing structure or integration needs go beyond what a platform template supports. Where a platform is genuinely the right fit for part of the problem — a 3D viewer, a documentation tool — we integrate it rather than rebuild it, and the surrounding system is still designed around your product.

Engagements run from roughly $25,000 for a focused design phase — such as a knowledge-base architecture or a dashboard design system — to $250,000 for a full custom portal or configurator with deep ERP integration. Every project is scoped in tiers: a mapping phase produces the specification and fixed price, a core release ships the highest-value workflows first, and extension phases add coverage. Published package ranges on this site are honest brackets, not teasers; the final number depends on integration depth and how much of your product logic must be encoded. The mapping session is where that number becomes concrete.