Case study based on a real commercial proposal, with identifying details removed. The industrial application described is illustrative.
A European engineering software vendor wanted to expand its market presence. Its tools covered piping and instrumentation diagrams (P&IDs), 3D plant modelling, piping isometrics and material take-offs. In France, the work would be to reach design offices, engineering firms and plant operators with established tools and delivery requirements. A commercial opportunity would begin when a team had a project worth evaluating the software on.
Starting with projects and the people who set the workflow
We cross-check the vendor’s existing accounts against industrial sites, the engineering firms that serve them and projects that can be documented. In France, we would begin with the Seine corridor in Normandy and the Lyon–Roussillon area. We would look for expansions, equipment replacements and piping modifications at existing plants. Each Myralbe MI record would include the reason for pursuing the account, its source and a question to check.
Several organisations may share the decision. The plant owner may specify file formats, an engineering firm may produce the drawings and the fabrication shop may spot missing information. We would record those roles and identify who could champion a trial. If the vendor already used a CRM, we would agree where to log activity and how to maintain a shared history without duplicating work.
From the first call in French to a meeting with the people who use the drawings
We start with the people closest to the work. In an engineering firm, that might be the design office manager or piping lead. At a plant, it might be the site engineering or capital projects manager. An opening question would be “When a pipe route changes, who updates the 3D model, the isometrics and the material take-off?”
If staff enter the same information in several tools, we ask for an example of a revision. If the owner requires a native file format, we identify who sets the requirement and what the file must retain. With an active project, we propose a meeting between the person producing the deliverables and the vendor’s specialist. Before a site visit, we agree which document or workflow to review and what decision the meeting could support.
Myralbe MI would record how we reached each person, whom we spoke to, what was emailed, what conditions the customer set and when to follow up. It would also show who could evaluate the tool, when the CAD or IT team should join and who would approve its use on a project.
Running a trial on a piping package the fabrication shop can review
Consider a plant replacing a pump skid. The design office needs to reroute several lines and issue drawings for prefabrication. Using an authorised dataset, the vendor and engineering team would select a few representative lines. The trial would cover bringing in the available data, changing the routing, producing isometrics and a material take-off, and applying a further revision to the affected documents.
We would compare initial setup, drawing production and revision effort. The receiving team would check the geometry, identifiers and attributes it needs. The vendor would run the demonstration and validate the technical result. We would prepare the session, document the findings and follow up until the teams could decide on the next project, users and training.
What the client sees each week and how we use it
The weekly report would show accounts researched and contacted, calls, direct messages, contacts identified, conversations, follow-up emails and meetings booked or held. Open opportunities would include the application, the question still to resolve and the next action. The client could see the detail in Myralbe MI and speak directly with us to change priorities or prepare its technical team.
If several engineering firms were receptive but faced the same file exchange barrier, we would bring that pattern to the vendor before extending outreach. If several sites struggled to manage revisions and one had a project available for testing, we would prioritise that application. Which deliverable needs to improve, who will check it and what decision can they make with the result?
