The same question, answered again
A distributor asks whether a product suits a particular temperature range or substrate. Sales forwards it to engineering, who answered something similar last quarter, in an email nobody else can find.
Make complex products easier to evaluate.
You may recognise some of this.
Not every team has every one of these. They are the situations that usually prompt the conversation.
Clarification by instalments
The first reply asks for operating conditions. The second asks which standard applies. By the third round the buyer has waited a week and the opportunity has cooled.
Answers that drift between markets
The datasheet says one thing, the translated brochure another and the sales deck a third. Engineering ends up correcting material it did not write.
From trigger to accepted result.
The work runs from a technical enquiry to a recorded next step. Most of the delay sits in the handoffs, not in the engineering judgement itself.
Step 1: Technical enquiry
- Sales or distributor support
- The enquiry and the customer's application details
- Logged against a product family and application, not simply forwarded.
Step 2: Requirement clarification
- Sales, using an agreed checklist
- The approved question set for that product family
- Missing conditions requested once, in one message.
Step 3: Suitability review
- Application or product engineer
- Approved answers, test data and known limitations
- A standard answer confirmed, or the case flagged as non-standard.
Step 4: Approved response
- Sales sends it; engineering approved the content
- The answer library, with applicability and limits
- The reply carries its evidence and states where it does not apply.
Step 5: Recorded next step
- Sales
- Your CRM or the system you already use
- Outcome logged; any new question goes back into the library.
What this looks like in practice.
An anonymised scenario drawn from patterns across our past work, showing how this kind of problem gets solved. Named projects follow further down the page.
One product family and its recurring questions
We take one product family and an agreed set of the application questions it attracts most often, then build the answers and the response workflow around them.
What you supply
- Datasheets, test reports and technical documentation for the product family
- A sample of recent enquiries and the replies that were sent
- Time with one application engineer for interviews and review
- Access to wherever enquiries are logged today
What you receive
- A source inventory: which documents hold which facts, and which are current
- Approved answers, each stating where it applies and its limitations
- Supporting evidence linked to each answer
- A response and review workflow with named owners
What stays with you
- Your engineers approve every statement of technical suitability
- You decide which questions are in scope
- You own the answers and decide where they are published
When it is complete
- Every in-scope question has an approved answer, or a recorded reason it needs case-by-case review
- The workflow has been used on live enquiries and adjusted
- Your team can maintain the library without us
Scope, fee, timing and how much of your team's time it needs are agreed in writing before any work starts.
Measured against your own starting point.
During scoping we agree a baseline for each measure from your own records, then compare at the end. We do not promise a percentage before we have seen the work.
From enquiry received to answer sent.
Engineer hours spent on repeat questions.
Messages exchanged before the requirement is clear.
Answers or materials corrected after they were sent.
Similar work, and why it is relevant.
Work by the people behind ECM.DEV, chosen because the workflow is similar, not because the sector is identical. Each case study says how it was delivered, and client names do not imply endorsement.
Product-Finding Tools for a Global Paints & Coatings Manufacturer's B2B Website
A product-attribute model that let B2B buyers narrow a large range by their own application. Approved application answers rest on the same structured product facts.
Read the case studyDigital Service Platform for a Building Materials Distributor
A service platform that put estimating, tendering and project documentation into professional buyers' everyday work, drawing on product data across CMS, PIM and ERP. Approved application answers depend on the same connected product information.
Read the case study
Founder · Fractional content operations lead
Senior ownership for the work between expertise, content and sales.
I help your team turn specialist knowledge into clear, approved material and repeatable workflows. That means connecting the people, information and systems needed to keep content useful across buying journeys and markets.
Start with one defined project. If you need continued support, I can lead agreed priorities, coordinate contributors and keep approvals and improvements moving, with a scope and rhythm that fit your team.
For manufacturers, that usually means sitting between sales and engineering until the answers stop needing both.
Start with one conversation.
A scoping conversation is about the work in front of you: which workflow, which material, who needs to be involved. If a first project makes sense, you receive a written scope and fee. If it does not, we say so.
- Understand the problem
- Agree one project
- Deliver and review
- Decide whether more is useful
A completed project with nothing further is a good outcome. Ongoing support is there if you want it, not a condition of starting.