Incomplete requirements
Customers may know the application, but not every technical or commercial parameter.
First-pass technical enquiry assistant
Turn incomplete technical enquiries into engineering-ready first-pass briefs.
A first-pass enquiry assistant for technical B2B sales teams — structuring requirements, flagging missing inputs and preparing a review-ready brief before engineering gets involved.
Human-in-the-loop · Engineers stay in control
Start with anonymised historical enquiries
ENQUIRY WORKSPACEIllustrative example
Incoming enquiry01
“We’re developing portable industrial equipment and need a rechargeable battery pack. Target is around 24V / 10Ah, initial annual volume about 1,000 units. The enclosure and charging approach are still being finalised.”
Requirements extractedKnown
- Application
- Portable industrial equipment
- Nominal voltage
- ~24V
- Capacity
- ~10Ah
- Expected volume
- ~1,000 / year
- Environment REVIEW
- Outdoor use? Unconfirmed
Needs clarificationMissing
First-pass outputReview
- Structured technical brief
- Missing-input checklist
- Possible development route
- Draft clarification response
Ready for human review
AI PREPARES THE FIRST PASSYOU MAKE THE CALL
Review first
Human approval before
customer-facing output
No guessing
Missing information
stays visible
Low-risk pilot
Start with anonymised
historical enquiries
Technical workflows
Designed around the
sales-to-engineering handoff
The starting point
Technical enquiries rarely
arrive quote-ready.
For custom and application-led products, the first task is often not quoting — it is turning an incomplete customer message into something sales and engineering can actually review.
Repeated clarification
Sales and engineering may need additional information before the right route becomes clear.
Messy handoffs
Requirements may be spread across email text, forms, drawings, BOMs and project notes.
Slow first response
The first useful response may wait until someone manually structures the enquiry.
From enquiry to clarity
A cleaner first pass
before engineering review.
- 01
Intake
Read the incoming enquiry, RFQ text or project notes.
- 02
Structure
Turn free-form information into explicit technical and commercial requirements.
- 03
Check
Flag missing, ambiguous or conflicting inputs before technical review.
- 04
Prepare
Create a first-pass brief and draft clarification response for human review.
A clearer brief. A better next question. Your team makes the technical decisions.
Real workflow demonstrations
See the workflow in action.
Two examples, one workflow: turn an incomplete enquiry into a clearer starting point for sales and engineering.
Battery enquiry
See an incomplete battery project turned into structured requirements, missing-input checks and a review-ready first pass.
Watch battery demo41 sec · Recorded workflow · Demo data
EGUO LABS / WORKFLOW EXAMPLE41 sec
View the recorded workflow Read the workflow summary
An incomplete 24V / 10Ah enquiry becomes a first-pass project brief. Dimensions, load profile, environment, charging, BMS and compliance remain open questions. Candidate development routes require engineering review; incomplete specifications are marked not quote-ready.
Power / product-selection enquiry
See requirements extracted from an incoming enquiry, missing specifications identified, suitable product directions surfaced and a first response prepared for review.
Watch power demo39 sec · Recorded workflow · Demo data
EGUO LABS / WORKFLOW EXAMPLE39 sec
View the recorded workflow Read the workflow summary
An illustrative charger enquiry is structured into requirements. Missing certification, delivery and colour specifications are highlighted, and plug type needs confirmation. Candidate products show matches and caveats before a draft response is prepared for review.
Illustrative demonstrations using demo data. A pilot is configured around your products, checks and review process.
Different products. A shared first step.
Built around technical
sales workflows.
Requirements to clarify
Custom packs & battery projects
- Application
- Voltage / capacity
- Dimensions
- Environment
- Peak current
- BMS
- Expected volumes
- Timeline
Shape the first-pass brief around the fields your team actually checks.
Requirements to clarify
Power supplies & transformer enquiries
- Input / output voltage
- Rating
- Load
- Duty
- Frequency
- Mounting
- Enclosure
- Compliance
- Quantity
Shape the first-pass brief around the fields your team actually checks.
Requirements to clarify
Cable assemblies & interconnect
- Connector
- Cable / wire specification
- Drawing / BOM
- Lengths
- Environment
- Quantity
- Alternatives
- Approvals
Shape the first-pass brief around the fields your team actually checks.
Requirements to clarify
Application-led electronic components
- Application
- Operating range
- Mounting
- Environment
- Interface
- Accuracy / tolerance
- Certification
- Quantity
Shape the first-pass brief around the fields your team actually checks.
The boundary is deliberate
A first-pass assistant —
not an autonomous engineer.
The goal is to remove repetitive intake work without removing technical judgement.
FIRST-PASS BRIEFHuman review
Human review stays in the loop
Nothing customer-facing needs to be sent without review.
Know when not to quote
The workflow can identify that an enquiry is not quote-ready instead of inventing an answer.
Missing information stays missing
Unknown technical data is surfaced for clarification rather than silently assumed.
Start without production integration
An initial pilot can use anonymised historical enquiries before connecting to live email or CRM systems.
Low-risk validation
Test it on a real enquiry.
Start with 5–10 anonymised historical technical enquiries. I’ll configure the first-pass workflow around your existing process and show the outputs before any production integration.
Discuss a pilot
Email Eric directlyeric@eguolabs.com
A practical starting point
- 01 Share anonymised enquiries
- 02 Configure your first-pass workflow
- 03 Review the outputs together
Built by Eric Guo.
Independent focus. Practical workflows.
I build lightweight workflow tools for technical B2B teams, with a focus on enquiry intake and the sales-to-engineering handoff.
Eric GuoEGuo Labseric@eguolabs.comA few useful answers
Before we talk.
Does this replace an engineer?
No. It prepares the first pass — structuring the enquiry, identifying missing inputs and drafting the next response. Technical judgement stays with the team.
Do you need access to our CRM or production email?
Not for an initial pilot. Validation can start with anonymised historical enquiries.
Can it work with custom products rather than a fixed catalogue?
Yes. The output does not need to be a SKU match. It can identify a likely route, highlight missing requirements and prepare the enquiry for engineering review.
What do you need for a pilot?
A small set of representative historical enquiries, the fields or rules your team normally checks, and enough product or process information to model the first-pass workflow.
What about sensitive customer information?
Initial validation can use anonymised enquiries. Data handling and integration requirements should be agreed before any live deployment.