# Trailcon + AMROD customer story rewrites **Date:** 2026-07-09 (format-matched to live customer stories) **Status:** Ready for Taylor review (Basecamp stays In Progress) **Sources:** Fathom transcripts on Basecamp cards 9818173282 (Trailcon) and 9866631059 (AMROD); May 2026 Word drafts treated as broken first passes **Quality bar:** TreasuryONE / Dunlop live stories in `customer-stories.part-a.ts` **CI:** US English, title case headings, full "and", no em/en dashes, Integration Development Environment spine (no iPaaS lead) --- ## Messaging-shift self-check - [x] Serves durable / governed integration layer thesis (not "how we did iPaaS") - [x] Does not lead with iPaaS or market-size stats - [x] AI not forced into stories where interview did not cover it - [x] Tone matches live site: engineering-led, declarative, anti-hype - [x] No invented metrics; qualitative outcomes where transcript has no number - [x] Customer stays the builder / owner of the architecture --- # 1. Trailcon Leasing ## Suggested index card outcome line > Millions of GL, AP, and AR transactions flow from TCL 360 into Sage Intacct. ## Diff vs previous draft (May 2026 Word) | Issue | What was wrong | What this rewrite does | |-------|----------------|------------------------| | Clarity | SEO-heavy, connector-promo asides, and a "bridge" story that never landed the stakes cleanly | Tight challenge → solution → result arc; stakes = finance pipe, not frontline ops | | Quotes | Weak / soft ("millions of transactions… going well"; partner praise) | Pulls the Dunlop-style criticality quote: pipe is tier-two critical for vendor pay and payment application | | Hallucination risk | Over-claimed "eliminated manual work" vibe; previous draft implied broader ops automation than Giovani allowed | Explicitly keeps front-end automation out of Flowgear's credit; Flowgear = GL/AP/AR pipe to Sage | | CI | iPaaS-era connector marketing ("For businesses connecting…") | Matches live story format: outcome-forward title, brief outcome chip, Challenge → Solution → Result → Quote → Ahead | | Outcome | Led on volume without the architectural point | Title and outcome lead with millions of GL/AP/AR transactions into Sage Intacct | | Format | Abstract spine language ("durable layer", "finance pipe") | Concrete headings and body copy aligned to TreasuryONE / Dunlop cadence | ## Quote audit (Trailcon) | Draft quote / claim | Transcript evidence | Status | |---------------------|---------------------|--------| | Pull quote: pipe critical for vendor pay / applying payments; not tier one for ops | @21:46–@23:23 Giovani: ops continue; backlog is accounting; "not tier one, but certainly tier two"; customers still get invoices; if bridge down, cannot apply payment in Sage | **Verified** (tightened for clarity; meaning preserved) | | ~14,000 owned trailers; manage ~25k–30k customer assets | @1:14 | **Verified** | | 8 locations; 150 technicians; 24/7 | @1:14 | **Verified** | | TCL 360 / Trailcon 360; Oracle shop; own TMS/ERP | @1:14–@5:55 | **Verified** | | MDX legacy; moved ops modules; left GL/AR/AP last; chose Sage (cloud / Intacct) | @6:05–@9:04 | **Verified** (ASR: "Sage Intact" → Sage Intacct) | | Introduced via Sage consulting partner (PureLogic / Moe and Faye on recording) | @9:08 | **Verified** (partner named on call; publish copy omits PureLogic) | | ~3 years customer; ~1 year to production; ~2 years effective use | @9:51–@10:00 | **Verified** | | GL + AP live; AR nearly complete | @11:01 | **Verified** | | No hours-saved stat; front-end automation is separate from Flowgear | @12:29–@14:54 | **Verified** (do not invent hours) | | Millions of transactions | @16:06 area / @21:30 context | **Verified** (qualitative volume) | | Avg 7–8 min to Sage; month-end ~400k txns in a few hours; latency up to ~3 hours | @16:06–@21:30 | **Verified** | | Without Flowgear they cannot send accounting info to Sage; important partner | @21:30 area | **Verified** | | Customer names Loblaw, Walmart | @1:14 | **Verified** | | "Pyrolator" | @1:14 ASR | **Flagged:** almost certainly Purolator; used Purolator in intro with audit note. Confirm with Giovani if naming in published copy. | | Giovani official title | Confirmed for publish | **Verified:** VP of IT Delivery, Trailcon Leasing | ## CustomerStory draft ```ts { slug: "trailcon", company: "Trailcon Leasing", sector: "Fleet leasing and maintenance", region: "Canada", outcome: "Millions of GL, AP, and AR transactions flow from TCL 360 into Sage Intacct.", summary: "Trailcon Leasing connected its owned TCL 360 operations platform to Sage Intacct with Flowgear, so GL, AP, and AR data can move at national fleet scale without putting technicians or customer invoicing on the same integration.", metaDescription: "How Trailcon Leasing uses Flowgear to move millions of GL, AP, and AR transactions from TCL 360 into Sage Intacct across a national trailer fleet.", systems: [ "TCL 360", "Sage Intacct", "General Ledger", "Accounts Payable", "Accounts Receivable", ], title: "How Trailcon moves millions of finance transactions from TCL 360 into Sage Intacct.", intro: "Trailcon Leasing has spent more than 30 years in trailer leasing, rental, fleet maintenance, and yard management. Headquartered in Brampton, just outside Toronto, the company serves Canada coast to coast from about eight locations. It owns around 14,000 trailers, manages roughly 25,000 to 30,000 customer assets, and fields about 150 technicians in a 24/7 operation that supports large fleet customers including Loblaw, Walmart, and Purolator.", challenge: { heading: "GL, AP, and AR still lived in a legacy system the business had outgrown", body: [ "For years Trailcon ran on MDX, a legacy system that once covered both operations and accounting when the company was much smaller. As the business grew, the team chose not to replace that stack with another vendor-owned platform. Instead it built TCL 360, an owned operations platform, and moved work orders, invoicing, AR management, and related modules out of MDX over time.", "The hardest remainder was finance: General Ledger, Accounts Payable, and Accounts Receivable. Trailcon did not want to build its own accounting system under regulatory and audit pressure, so it selected Sage Intacct in the cloud. The open question was how to move the intelligence that already lived in TCL 360 into Sage in a reliable way.", ], }, solution: { heading: "Flowgear as the bridge from TCL 360 into Sage Intacct", body: [ "Trailcon was introduced to Flowgear by its Sage consulting partner. Giovani Cani initially questioned why a third company belonged in the architecture at all. The answer was practical: Sage would not own that connection, and Trailcon needed a dependable path for audited finance data.", "Flowgear became the bridge for GL and AP entries into Sage Intacct, with AR close to completion at the time of the interview. The work was not only a migration. It supported a re-engineering of the chart of accounts and dimensions so reporting could match how leadership needed to see the business. Officially a Flowgear customer for about three years, Trailcon had been sending production data for roughly two years after about a year of build-up.", ], }, result: { heading: "Millions of transactions moving, with month-end as the stress test", body: [ "Trailcon still generates customer invoices from its own platform, sometimes thousands overnight. Those invoices create GL entries that must reach Sage so vendor payments, payment application, balances, and audited reporting stay current. Giovani describes the volume as millions of transactions moving through the integration.", "Under normal load, a transaction created in Trailcon's system reaches Sage in about seven to eight minutes on average, which meets the requirement. At month-end the picture changes: around 400,000 transactions can land within a few hours, driven by depreciation and other asset-heavy records across a large fleet, and latency can stretch toward three hours. Tuning that spike is the next engineering job.", ], points: [ "GL and AP flowing into Sage Intacct; AR nearing completion", "Millions of finance transactions moved through the integration", "Typical latency about 7 to 8 minutes from TCL 360 into Sage", "Month-end peaks around 400,000 transactions in a few hours", "Operations intentionally decoupled from the Sage Intacct sync", ], }, ahead: { heading: "Finish AR, then bring month-end latency back under control", body: [ "Trailcon's near-term focus is completing AR, then optimizing high-volume month-end loads so reporting and vendor payment cycles stay manageable. Flowgear is now how accounting data reaches Sage Intacct, even though frontline repair work was deliberately kept off that dependency.", ], }, quote: { text: "Operationally we can still run. Work orders and repairs continue, and customers still get their invoices from our own system. But the pipe has to keep running. If it backlogs, that hits paying vendors and applying payments in Sage. It is not tier one for the roadside technician, but it is certainly tier two for the business.", name: "Giovani Cani", role: "VP of IT Delivery, Trailcon Leasing", }, featured: true, } ``` ### Notes for Rixie / publish - Giovani title confirmed: VP of IT Delivery, Trailcon Leasing. - Confirm Purolator naming (ASR: "Pyrolator"). - Do not claim hours saved; Giovani declined that framing and attributed process-time gains mainly to front-end work outside Flowgear. - Logo: not in workspace yet; add when available. --- # 2. AMROD ## Suggested index card outcome line > A monthly SYSPRO PO and GRV process that took one person about a week now runs daily in under a minute. ## Diff vs previous draft (May 2026 Word) | Issue | What was wrong | What this rewrite does | |-------|----------------|------------------------| | Clarity | SEO keyword block, connector CTAs, and a "Platform" section that diluted the story | Single clear arc matching live format: Challenge → Solution → Result → Quote → Ahead | | Format | Abstract title ("durable layer between systems") | Outcome-forward title: week of monthly SYSPRO work to daily run in under a minute | | Quotes | Multiple highlight quotes; primary pull was soft "makes the complex simple" without the production stake | Primary pull = Corne's 2–3 weeks custom vs ~2 days in Flowgear (concrete). Llewellyn visual quote kept as secondary option | | Hallucination / CI | "iPaaS platform" in SEO; golf-day origin overplayed; breakfast / founder social color risk | No iPaaS lead; origin kept to one factual sentence; no Cape Town dinner anecdotes | | ASR | Draft correctly used SYSPRO (transcript ASR: "CISPRO") | Keep SYSPRO; documented in audit | | Titles | Draft attributed quotes to "AMROD" only | Names and titles confirmed: Corne = Development Manager; Llewellyn = Senior Software Consultant | ## Quote audit (AMROD) | Draft quote / claim | Transcript evidence | Status | |---------------------|---------------------|--------| | Primary pull: 2–3 weeks custom vs ~2 days in Flowgear (Moyo-related change) | @17:00 Corne de Beer | **Verified** | | Secondary option: "makes the complex simple" / visual flow | @19:16 Llewellyn Breedt | **Verified** (optional; not primary) | | CV / career enablement quote | @18:03 Corne | **Verified** but weaker for story object; omit from primary page unless needed | | Custom ERP; long QA/regression; need to decouple for time to market | @3:05 Llewellyn | **Verified** | | ERP vision tied to Nimrod (director); box-tracking origin | @4:24 | **Verified** (one clause only; no invented founder anecdotes) | | Found Flowgear via CTO Etienne / golf conversation referral | @5:04 | **Verified** (one sentence; no named third party) | | Moyo = heartbeat in Swahili; replacing Amtrak/current ERP; Flowgear already in design | @5:36–@6:06 Corne | **Verified** (ASR also says "Mojo"/"Moyal"; use **Moyo**) | | CTO direction: no system-to-system direct talk; move integrations into Flowgear | @6:42 Llewellyn | **Verified** | | SYSPRO international PO/GRV: ~1 week/month, one person; built in Flowgear in <1 week; runs daily <1 minute | @7:54–@9:50 Llewellyn | **Verified** (ASR: CISPRO → SYSPRO) | | Current ERP ~19 years; rough Moyo ETA end 2027; adding squads | @11:09–@12:21 | **Verified** | | Avoided million-per-year ESB recommendation in 2016 WMS project | @13:14 Llewellyn | **Verified** (context for why Flowgear beats heavyweight middleware / home-grown ESB maintenance) | | Customer ~3–4 years; first integration around website launch post-COVID 2021–2022 | @2:26–@2:40 | **Verified** | | Official titles for Llewellyn and Corne | Confirmed for publish | **Verified:** Corne de Beer, Development Manager, AMROD; Llewellyn Breedt, Senior Software Consultant, AMROD | | Breakfast / Cape Town social color | Opening small talk only | **Excluded** per brief | ## CustomerStory draft ```ts { slug: "amrod", company: "AMROD", sector: "Promotional products", region: "South Africa", outcome: "A monthly SYSPRO PO and GRV process that took one person about a week now runs daily in under a minute.", summary: "AMROD is moving integration out of its custom ERP and into Flowgear, starting with finance-critical SYSPRO purchase order and GRV automation, and carrying the same approach into Moyo, its next internal ERP.", metaDescription: "How AMROD uses Flowgear to automate SYSPRO PO and GRV work, cut a week of monthly finance processing to a daily run in under a minute, and support Moyo, its next-generation internal ERP.", systems: [ "Custom ERP (Amtrak)", "Moyo ERP", "SYSPRO", "Warehouse systems", "Website and payment portals", ], title: "How AMROD cut a week of monthly SYSPRO work to a daily run in under a minute.", intro: "AMROD is a South African supplier of promotional products, corporate gifts, clothing, headwear, and branded merchandise. Behind the catalogue sits a deeply custom technology stack. For nearly two decades a home-grown ERP has sat at the center of ordering, credits, approvals, warehouse links, website payment portals, and much of the financial work outside month-end. That control came with a cost: every integration change lived inside the core system.", challenge: { heading: "Every integration change meant another trip through the core ERP", body: [ "AMROD's ERP combined data from surrounding systems and owned the integrations between them. Any change had to be built in that core, then pushed through a long development, QA, and regression cycle before release. For a business measured on time to market, that cycle was the bottleneck.", "The team needed to decouple integration from the ERP so delivery could speed up without putting the systems that run the business at risk on every change. A recommended enterprise service bus during a 2016 warehouse project had already shown the other extreme: licensing in the millions per year. Building everything internally avoided that bill, but left AMROD maintaining heavy integration code itself.", ], }, solution: { heading: "Move integrations into Flowgear, including the path into Moyo", body: [ "AMROD adopted Flowgear after its CTO raised the integration problem and was pointed at the platform. The direction from leadership is explicit: systems should not talk directly to each other. Integrations move into Flowgear one by one.", "That same pattern is already part of Moyo, the next internal ERP now under design. Moyo means heartbeat in Swahili, and it is intended to replace the current ERP after roughly 19 years of accumulated development. Flowgear is not a side tool for the old stack. It is designed into the replacement.", ], }, result: { heading: "A week of monthly finance work now runs daily in under a minute", body: [ "One of the clearest early wins sits in international purchase order and GRV processing with SYSPRO. A finance team member used to spend about a week every month checking overseas receipts, creating GRVs against purchase orders, and manually posting the related records because SYSPRO could not automatically access the arrival data.", "AMROD built the Flowgear workflow in less than a week. After QA and UAT, it runs daily in under a minute, closing POs from ERP and SYSPRO data and processing the financial records. Separately, a recent Moyo-related change that would have taken two to three weeks as custom code was stood up in Flowgear in about two days.", ], points: [ "International SYSPRO PO and GRV flow automated", "About one person-week of monthly finance work reduced to a daily run under a minute", "Workflow built in Flowgear in less than a week", "Recent Moyo-related change: about two days in Flowgear vs two to three weeks custom", "CTO mandate: no direct system-to-system integrations; Flowgear is the path", ], }, ahead: { heading: "Replace the ERP, keep the integration layer", body: [ "AMROD's primary focus is still moving remaining integrations out of manual and custom paths into Flowgear while Moyo is built. The current ERP is estimated at about 19 years of development. Delivery is roughly aimed at the end of 2027, with additional squads being added to push harder. Flowgear is intended to carry both the current estate and the replacement.", ], }, quote: { text: "There was a recent change we had to do for Moyo. If we went the custom route, it would have taken us two or three weeks to develop that piece of code. We set it up in Flowgear in about two days, and it was running.", name: "Corne de Beer", role: "Development Manager, AMROD", }, featured: true, } ``` ### Optional secondary quote (not primary pull) > "It makes the complex simple. Integration code is messy. Flowgear gives you a visual of what is actually happening. You can read it like a flow diagram and understand it in a few seconds." > — Llewellyn Breedt, Senior Software Consultant, AMROD ### Notes for Rixie / publish - Titles confirmed: Corne de Beer, Development Manager, AMROD; Llewellyn Breedt, Senior Software Consultant, AMROD. - Logo exists in site assets: `amrod-logo-color.webp`. - Do not add founder dinner / Cape Town social anecdotes. - Prefer Corne's two-day quote as the page pull; Llewellyn's visual quote is strong but less stake-heavy. --- ## Hand-off 1. Taylor reviews both `CustomerStory` objects above. 2. On approval: paste into `customer-stories.part-b.ts` (or new part file), add logos. 3. Only then move Basecamp cards / send to customers for sign-off. 4. HubSpot-style index card layout remains a separate Jason card; these objects are written for clarity first.