Bring the Problem — Not Your Secrets Yet
Start with a short, non-confidential summary of the technical problem, the route your team is considering, and the decision you need to make. If there is a fit, deeper details can follow under appropriate confidentiality arrangements.
What to Send First
The first message should help me understand the shape of the problem without requiring you to disclose formulas, drawings, proprietary data, supplier details, customer names, or confidential technical strategy.
The current problem
What is stuck, failing, drifting, too slow, too costly, or difficult to decide?
The current route
What is the team planning to investigate, test, buy, change, scale, or abandon?
The decision
What decision does the next piece of technical work need to support?
A Good First Message
“We are considering a two-month investigation into a recurring process problem. The team has a plausible cause, but we are not sure whether finding the cause would change the decision. We would like help checking whether there is a better route before committing the work.”
That is enough to start.
Contact Form
Send a short, non-confidential message. Please do not include confidential formulas, proprietary data, drawings, customer names, supplier names, or trade secrets in the first message.
If the form does not open your email app, email directly: aleczhou@robustsolutionspro.com
Useful Details to Include
A few clear points are more useful than a long technical file at the first step.
Technical area
For example: formulation, process, product, scale-up, quality, equipment, drying, mixing, modeling, or documentation.
Current path
What is the team currently planning to investigate, test, buy, change, scale, stop, or continue?
Desired outcome
What would make the conversation useful? A better route, a smaller test, a clearer decision, or a second opinion on the current plan?
Please Leave Out at First
The first message should stay non-confidential. More detailed technical information can be handled later if the fit and confidentiality process are clear.
Please do not submit: trade secrets, confidential formulas, proprietary data, drawings, internal reports, detailed process parameters, customer information, supplier information, or patent-sensitive details through the first contact form.
SR&ED: I support the technical side of R&D work, including problem framing, investigation logic, evidence, learning, and technical documentation. I do not provide tax, accounting, legal, eligibility, filing, refund, or CRA opinions.
Intellectual property: I can help explore technical alternatives and constrained routes. I do not provide patentability, infringement, freedom-to-operate, or legal opinions. Those require qualified IP counsel.
Ready to Check the Route?
Send a short, non-confidential summary of the technical problem, the current plan, and the decision your team needs to make.