dorel juvenile · workflow deep-dive

Walk the cotización + PO workflow end-to-end with Nicolás.

Interviewee: Nicolás Errázuriz · nicolas.errazuriz@dorel.cl · role TBD (Block A)
Sponsor (not on call): Gustavo, Country Manager, Dorel Juvenile Chile

What we want out of this call

Understand Nicolás's role and team so we know whose vantage point we're getting.
Walk the full workflow end-to-end — cotización generation + PO entry into Dynamics. Step by step, who does what, where time goes, where it breaks.
Confirm the data points — volume, time, conversion.
Land the pain in Nicolás's own words.
Close with decision-making + next steps — who signs, budget shape, the IT scoping call gate with Kiko.

who's who going in

sponsor · not on call

Gustavo

Country Manager, Dorel Juvenile Chile

Joined October 2024; delivered the 2025 turnaround (-12% → +0.4% EBIT, 12-point swing).
Org: 330 employees, 200+ in retail. 47 stores; closed 7-8 underperformers.
Working 12am-1am leading canal tradicional himself until the new hire ramps end-June.
Personal language: "rentabilizar la empresa, aumentar la última línea."
Reports into Dorel Industries Canada (listed). Canadá CIO must align on tooling.
Lives Vitacura/Santiago + Italy. Speaks ES/PT/IT. Wife is Chilean.
Considering AWS Bedrock for governance and Ley 21.719 compliance.
Came to us via Adrián (AI assessment voice agent).

interviewee · today's call

Nicolás Errázuriz

Role TBD — confirm in Block A

Email + name only going in. Open questions:

Role + title at Dorel Juvenile Chile
Tenure
Relationship to Gustavo (direct report? peer? IT?)
Team composition
Commercial / Ops / IT / Digital
Is he the new hire starting end-June, or someone else?

keep in mind during the call

01
Listed-company governance. Canadá CIO has to align. Chile is "disruptive" but cannot decide unilaterally.
02
Ley 21.719 Chile deadline 1 December 2026. GDPR-style. Six months out. Drives the Anthropic vs AWS Bedrock decision.
03
Three concurrent ERP-adjacent migrations. Dynamics → TOTVS (Apr 2027), Insider → Vera's CDP, Devenet → GoSocket.
04
Build internally already exists. Kiko (planning lead) built an internal CRM that does quote → approval. The Dynamics-write step was never wired. Built on personal Microsoft credentials.

main section · the questions

What we ask Nicolás

Six blocks. Block B and C are the meat of the call — the workflow walk-through, end to end. A is quick rapport. D-E support B/C. F closes. Click any block to expand.

Role and team

6 Qs · ~5 min · open the call

Goal: learn whose vantage point we're getting. Brief, builds rapport, sets up everything else.

Confirm his role, title, and time at Dorel Juvenile Chile.

Team composition: who reports to him, how many people, what disciplines?

Where does his team sit in the org chart? Sales, Ops, IT, Commercial, Digital?

Relationship to Gustavo — direct report, peer, project owner for this initiative?

How was he introduced to AdapttoAI? Through Gustavo directly, the AI assessment, somewhere else?

Is he the new hire starting end of June, or has he been at Dorel longer?

The cotización workflow (end-to-end)

10 Qs · the meat of the call

Goal: walk a single typical cotización from inbound request to "client approves." Step by step. The Loom video is the gold standard; this is the verbal version.

Walk us through a typical cotización from start to finish. Who initiates it, who prepares it, who approves it internally, who sends it.

Where does the product info come from when preparing the quote? Catalog in Dynamics, Excel sheets, memory, the internal CRM?

Where does pricing come from? Standard list? Negotiated per-client list? Discount discretion?

Where does stock visibility come from when quoting? The data warehouse (per the May 29 transcript), Dynamics directly, or somewhere else?

Is there a quote template? Word? Excel? Custom CRM output? PDF?

How is the cotización delivered to the client? Email, WhatsApp, PDF attachment, portal?

How does the client respond and approve? Format of the approval (email, signed PDF, voice, in-CRM action)?

What changes mid-flight — price negotiation, line item swaps, quantity changes? How is that handled?

Common failure modes: where do quotes get stuck, lost, mis-priced, or sent late?

B10

The internal CRM: what does it actually do today for cotizaciones? What's the experience for the operators using it?

The PO entry workflow (approved → Dynamics)

7 Qs · the second half of the workflow

Goal: understand the manual handoff from "client said yes" to "PO exists in Dynamics." This is where the ~5 min/PO claim lives.

Walk us through the PO entry process from approved quote to PO created in Dynamics. Step by step.

Who does this entry today — the same two operators who prepared the quote, or different people?

What exactly happens in Dynamics during those ~5 minutes? Data entry, stock validation, pricing check, customer lookup, all of the above?

What validations or approvals fire after PO entry? Credit check, stock allocation, manager sign-off?

What happens downstream after the PO is created? Allocation, picking, shipping, invoicing. Automated or manual?

The internal CRM was built to push approved quotes into Dynamics as POs but never activated. From Nicolás's view: what specifically blocked that activation?

If the CRM had worked end-to-end (CRM → Dynamics PO), what % of the current manual time would have been recovered?

Volume and time

6 Qs · exact numbers, not directional

Goal: replace directional claims with exact numbers. Pricing and ROI both depend on this. If he doesn't have the numbers live, send as written follow-up.

Cotizaciones per week (canal tradicional specifically). We have no number for this.

POs per week. Transcript suggests ~200 (2 operators × ~25/day). Confirm.

Conversion rate quote → PO.

Average PO value. Distribution: lots of small repeats, or long tail with a few large?

Seasonality. Peak weeks vs trough weeks. Back-to-school, holidays, fiscal close?

Client count. Canal-tradicional accounts vs key accounts vs farmacia vs wholesalers vs ecommerce.

Pain and impact

5 Qs · specific quotes only

Goal: specific quotes Nicolás will recognize as his own when paraphrased in a proposal. Generic pain is dead pain.

From Nicolás's vantage point: what's the worst part of this workflow today?

Cost of NOT fixing it — lost deals, operator burnout, errors, compliance risk under 21.719, pressure from the TOTVS migration?

What do the two canal-tradicional operators say about the work? Errors that keep happening? Things that feel like wasted time?

Why has this not been solved internally already? The CRM was built — what's the real story behind the activation gap?

The new hire end-of-June: do they inherit this pain, or are they expected to have a clean workflow by then?

Decision-making and next steps

6 Qs · close the call here

Goal: confirm who signs, the path forward, and set up the technical follow-up with Kiko.

Who decides to move forward with an external partner like AdapttoAI? Nicolás himself, Gustavo, Canadá CIO?

Budget shape — project cap, OPEX subscription, or mixed? Fiscal-year window?

Approval threshold below which Chile can decide independently of Canadá?

Timeline — realistic target for having something live? Before TOTVS migration (Apr 2027)? Before the 21.719 deadline (Dec 2026)?

The IT scoping call. Standard pattern for us: 30-min technical call with Kiko + Dynamics auth owner before we land a price. Frame: "this is how we make sure the price holds." Get it scheduled.

Operational asks for the next two weeks: Loom video of the workflow, direct call with the operators while they're still there, direct call with Kiko.

decisions before the call

3 decisions we need to settle first

☐
Lead with Block A or Block B? Suggestion: Block A first (5 mins, builds rapport, frames everything). Then dive straight into Block B+C — the workflow walk-through is the point of the call.
☐
Bring the IT scoping call up live, or in follow-up email? Suggestion: live, at F5. "We've found that the cleanest way to land a fair price is a 30-min technical call with whoever built your CRM. Can we get that with Kiko for next week?"
☐
Do we send Block D as written follow-up, or push for live answers? Suggestion: ask live, but if he doesn't have the numbers, send Block D as a written follow-up for him to route to whoever has the data.

appendix · reference material

A.1 What we already have on Dorel

From this repo

b2b/pipeline/dorel-juvenile/status.mdPipeline state, contact info, open questions.
b2b/pipeline/dorel-juvenile/2026-05-29_Dorel Juvenile.txtFull May 29 transcript with Gustavo + Raffaello.
b2b/pipeline/dorel-juvenile/scoping-questions-v2.html10 external questions sent. Awaiting answers + Loom video.
b2b/pipeline/dorel-juvenile/bootcamp.htmlWorkshop option teed up.

From the AI Assessment project

v2 maturity report (live): adapttoai-dorel-juvenile.pages.dev
~/Claude Code/AI-assessment/docs/reports/Dorel Juvenile/dorel-juvenile-2026-05-27-v2.html
~/Claude Code/AI-assessment/docs/deep-research/dorel-juvenile/deepresearch_dorel-juvenile.mdDeeper diagnostic with stack map + per-pain tool comparisons.
~/Claude Code/AI-assessment/docs/transcripts/2026-05-22_dorel-juvenile

Volume + time baseline (refined from May 29 transcript)

Supersedes the "~10 POs/week" number in the earlier status.md.

Two operators on canal tradicional, ~25 POs/day each → ~200+ POs/week.
~5 minutes per PO in Dynamics manual entry → ~16-20 hours/week of pure manual entry.
90% of those two operators' time is reactive ops, 10% proactive selling.

A.2 Systems detail — for the Kiko follow-up, not this call

Save these for the technical scoping call. Asking them today would burn time on questions Nicolás may not be able to answer.

Dynamics version. "2012" mentioned. AX 2012? GP 2012? NAV 2012? 365 Business Central? On-prem vs cloud?
Internal CRM stack. What's it built on? Where hosted? Personal credentials story?
Snowflake. Schemas populated, source systems, who has write.
Power BI. Reports active for canal-tradicional or only finance/exec?
Microsoft 365 + Teams Premium. Rollout status.
Claude Enterprise. Refund processed? Replacement plan?
AWS Bedrock. Canadá CIO decision status.
TOTVS. April 2027 firm? Partner engaged? Staging environment? Module choice?
Insider → Vera's CDP. Status, Snowflake connector confirmed?
Devenet → GoSocket. Status.
Supply5. Active for demand forecasting? Will it survive TOTVS?
Personal-credentials CRM cleanup. Plan + 21.719 deadline.

A.3 Aronlight RFQ agent — validated workflow reference

Live in production at Aronlight (Manel Vidigal, PT/ES). Repo: ~/Claude Code/aronlight-erp-research/. Brief: docs/brief-for-riccardo.md.

Dimension	Aronlight	Dorel signal
Business model	B2B distribution (lighting)	B2B distribution (puericultura)
Workflow shape	Quote then order, two flows	Cotización then PO, two flows
Current bottleneck	Manual SKU by SKU in Odoo	Manual SKU by SKU in Dynamics
ERP	Odoo v18 XML-RPC	Microsoft Dynamics now, TOTVS April 2027
Internal pre-build	None	CRM does quote-and-approve, missing the ERP-write step
Volume	~3,000 RFQs/month	~800-1,000 POs/month estimate

A.4 Argea — ERP scoping-call discipline

Repo: ~/Claude Code/argea-sap-research/. The discipline we want to import: "The SAP IT scoping call is a mandatory pre-condition for kickoff. Target: 30-min call in week 1 after signing." For Dorel, the equivalent is the Kiko + Dynamics auth scoping call.

A.5 Proposal shape (gated, do not share)

track a · primary

Cotización + PO generation (Aronlight shaped)

MVP scope. Extend the internal CRM with the missing Dynamics-write connector, or build the connector ERP-agnostic if the migration plan lands on adapter-pattern.
Phases. 6 to 10 weeks depending on Block B+C answers.
Billing. V3 cadence (Mes 1 implementation, Mes 2 $0, Mes 3+ monthly). Floor $10K/yr.
Implementation fee. Medium-High complexity (30-40% of annual subscription).

track b · optional, parallel

AI literacy + governance workshop

Shape. 1 to 2 workshop sessions: back-office AI literacy + Bedrock vs Anthropic + token cost control.
Sized. ~$18K range (similar to Essedi / BCP precedent).

pre kickoff gate · argea shaped

30 minute Dorel IT scoping call before any number lands

Attendees:

Kiko (CRM builder). What exists, what credentials, what API surface.
Whoever owns Dynamics auth. What writes are allowed, what auth path.
Whoever speaks for the Canadá CIO. Bedrock or Anthropic, sign-off path.

If this call cannot happen pre-signing, the proposal carries the same caveat Argea's does: "If scoping call delays > 3 weeks from signing, V1 timeline shifts."