An initial market-development assignment should leave a manufacturer able to explain which applications deserve attention, which accounts justify further work and what is needed to move them forward. The review needs evidence of commercial progress and an honest account of what remains unproven.
The ninety-day outline below is an illustrative planning framework. Myralbe defines each market-development assignment individually, according to the supplier’s starting position, product and objectives. Review dates and deliverables should reflect the buying process and available resources. The phases can overlap, and commercial milestones also depend on buyer participation and approval.
Days 1–30: establish a defensible starting position
The first review should test whether the team has a sound basis for approaching the market. A broad industry label is insufficient. An application brief should describe the process or problem the product addresses, the operating conditions that matter and the evidence supporting its proposed value.
For an industrial component, that might mean documenting compatibility requirements and the consequences of replacement. For technical software, it might mean defining the engineering workflow, required integrations and who would evaluate a trial. These are working hypotheses to verify through conversations.
The account map should explain why each organisation belongs in scope. Useful entries identify the relevant site or business unit, likely application, known contacts, source of the information and unanswered questions. Priorities should be explicit enough for the manufacturer to challenge.
Manufacturer input is essential here: product documentation, application references, commercial boundaries and existing account history. Protected accounts, current opportunities and contact restrictions should be recorded before outreach. Named supplier specialists should own technical answers, with an agreed response process. These responsibilities belong in planning an outsourced sales pilot.
At day 30, review the application brief, prioritised accounts, approved approach and outstanding dependencies. Decide whether to proceed with the proposed focus, narrow it or resolve missing product evidence before extending activity.
Days 31–60: turn contact into usable evidence
Direct outreach in the local language should test the account assumptions. The record needs to show whom the team reached, what that person actually influences and what was learned. A job title alone does not establish responsibility for specifying, evaluating or purchasing the product.
A useful conversation record captures the application discussed, current approach, stated requirements, timing and agreed next action. It also distinguishes buyer statements from the team’s interpretation. “Interested in a presentation” and “evaluating an alternative for a named application” should remain different descriptions.
Formal access deserves equally careful treatment. Endesa’s published purchasing process identifies supplier qualification, purchase-request management, the award process and contract formalisation as separate steps. The practical implication for a progress review is that supplier qualification is a meaningful milestone, while evidence of a live requirement and buying decision still needs to be established.
The day-60 output should therefore include updated account priorities, decision-role information, conversation records and a requirements register. Where specialist input is needed, each question should have a supplier owner and an agreed next action. Technical briefings should give that specialist the customer’s context before the conversation.
This review should also examine negative evidence. A confirmed mismatch in operating requirements may justify removing an application. Repeated absence of the assumed problem may justify changing the segment. Unanswered outreach leaves an account unresolved; it does not prove that demand is absent. Record these distinctions so that a revised focus has a visible rationale.
Days 61–90: show what can progress and what it requires
The final period should deepen the strongest evidence and make the next commercial steps concrete. Depending on the product and the customer’s process, that may involve a specialist discussion, an application review, a trial definition or a proposal. Buyer participation and internal approvals determine whether those steps occur.
Where a trial is appropriate, the record should identify the question it must answer, the proposed conditions, who evaluates the result and what remains to be agreed. Where a proposal is justified, the manufacturer should have a documented requirement and the information needed to prepare it. Proposal follow-up should capture customer feedback, outstanding questions and the next agreed action.
The manufacturer remains responsible for the technical answers and commercial approvals assigned to it. If progress depends on an unavailable sample, an integration assessment or an unconfirmed delivery commitment, the review should show that dependency explicitly. This helps both sides decide what resources the next phase needs.
By day 90, the client CRM or agreed reporting should contain a coherent account history, current status, open requirements, proposal information where applicable and named owners for follow-up.
Use the review to decide the next phase
The decision should draw on three questions: which assumptions have support, what remains unresolved and what further work would change the commercial assessment?
Continuing development may be justified where relevant accounts have confirmed a need and there is a credible next step. Narrowing the scope may be appropriate where evidence clusters around one application or account type. A pause can be the useful outcome when product readiness or supplier resources prevent meaningful evaluation. Any extension should have a defined question to resolve.
Evaluate controllable work against the agreed scope: research completed, accounts assessed, outreach conducted, information recorded and follow-up maintained. Evaluate buyer outcomes separately, using the evidence available. Neither meeting volume nor an attractive pipeline total can replace that judgement.
Finally, make continuity explicit. If an internal salesperson takes over, provide the account context, contact boundaries, commitments already made and outstanding actions, and agree introductions where needed. The work should remain usable after the review.
Considering development in Spain, Portugal or France? Contact Myralbe with your product, target market, existing accounts and desired commercial outcome so that the initial scope and review points can be defined.
