Video summary

Scaling to $140M with Offshore Team: The Culture and Systems Behind TOA’s Growth with Nick Sinclair

Main summary

Key takeaways

Business

TOA Growth (Nick Sinclair): Scaling to ~$140M with Offshore Teams—Culture & Systems

Company scale & footprint

  • Scaled to >$140M revenue and >4,500 employees across 5 countries
    • Plans to expand into 3 more countries “this year”
  • Client mix:
    • 60% Australia + New Zealand
    • 40% North America, with a goal to shift toward 70% North America as an American business
  • North America expansion plan:
    • “Nail” the US, then expand into Canada (described as bigger than Australia)
    • UK expansion likely via acquisition (to buy established competitors/players)

Origin story → offshore as a “side hustle” that became the core business

  • Started as a financial planning + accounting firm, aiming to “add more value” to clients—e.g., managing cash flow and helping clarify where money is spent (beyond investment advice).
  • Offshore breakthrough:
    • Tried outsourcing in different countries; it didn’t work initially
    • Found an outsourcing partner in the Philippines, then built offshore bookkeeping/operations
  • Go-to-market via board / speaking circuit:
    • A board chair put him on stage to explain outsourcing’s impact on pricing (including AU/outsourcing wage arbitrage such as $20/hr vs $100–150/hr for bookkeeping)
    • Early objections (“outsourcing takes jobs away”) were met with demand:
      • After the first 3 roadshows: 5 firms offered support (e.g., spare desks in Australia/region) and adoption
  • Sales milestones:
    • 100 people within ~12 months
    • 200 next year
    • Then ~380 the following year
  • Decision to go all-in:
    • The side-hustle hit a breaking point—couldn’t run both businesses (late nights; two kids under age 4)
    • Chose offshore outsourcing as the scalable path, building a business less dependent on his personal involvement

Growth philosophy & why founders “get stuck”

  • Key management diagnosis:
    • Founders often fail because “everything’s in their head”—they don’t document or train, making delegation impossible
  • Leadership evolution:
    • Early approach emphasized control and having “the opinion” in every situation
    • As the company scaled, he learned leadership requires empowerment and “getting out of the way”
  • Lesson learned:
    • Businesses outgrow people, and promotions can set high performers up to fail if their capability doesn’t match the next role

Offshore team playbook (what TOA gets right)

Common failure mode (and the TOA counter)

  • Failure: treating offshore staff like outsourced labor instead of a true internal team
  • TOA principle:
    • If you had an office in another city, you’d visit—so offshore teams expect at least annual in-person connection
    • Include offshore teams in meetings, rhythms, communication, and culture

Delegation & training systems (process > “black and white” instructions)

  • Early mistake:
    • Delegated the wrong tasks and assumed offshore hires would figure it out
    • Communication needed to shift from “direct + outcome orders” to a bouncing ball + process + systems
  • Delegation framework:
    • Offshore work must start with structured context, not “do it and figure it out”
    • Avoid “magical unicorn expectations” (expecting instant manager-level capability)

Where to start with offshore (phased onboarding)

  • Recommended first tasks:
    • Calendar management
    • Email management (even as simple as folders)
  • Typical “first 6 weeks” approach:
    • Only a few hours/day initially
    • If needed, fill remaining time with research tasks
    • Avoid meaningful complex work at the start

Talent model: deep and narrow + scalable career ladders

  • TOA focuses deep and narrow:
    • Primarily supports accounting firms
    • Built tech, marketing, systems, communication, meeting rhythms, and client service around accounting-firm needs
  • Capability ladder example:
    • Clients can place team members offshore up to manager levels
      • Example: a San Antonio firm with 10 managers, 5 in the Philippines managing US + local teams
  • Staged complexity principle:
    • Don’t start offshore with the most complex tasks—build capability gradually
  • Concrete domain example:
    • Healthcare outsourcing pattern:
      • initial X-ray reports in the Philippines
      • then reviewed/sign-off elsewhere

Organizational systems & operating cadence

North Star & KPI focus (lightweight dashboarding)

  • Uses one North Star metric:
    • Net commencements = people starting weekly vs leaving (retention/growth signal)
  • Additional operational view:
    • “Growth dashboard” and a finance meeting once a month
  • Emphasis:
    • Don’t need “140 dashboards” if leadership is driven by clear metrics and operating rhythms

Culture & engagement “system” (to maintain standards remotely)

  • Tool: Culture plan (personalization at scale)
    • Capture meaningful info (partner, kids, birthdays, anniversaries, hobbies)
    • Use process reminders (e.g., EA schedules prompts so leaders don’t have to remember)
    • Tie engagement to key dates with consistent execution
  • Recognition preference:

    • Offshore employees often prefer experiential “wow/delight” gifts over cash (e.g., spa/nails/hair/massage/trips)
  • Engagement plan cadence:

    • Monthly events in the Philippines (e.g., Valentine’s, Mother’s/Father’s Day, and “year-end” events instead of “Christmas” for religious diversity)
    • Example of syncing celebrations globally (e.g., Melbourne Cup event with the team in the Philippines)

Strategy & future targets (growth roadmap)

Stated targets

  • $500M revenue goal
  • 10,000 team members
    • Framed as a community-impact strategy: well-paid work → local economic impact

Market expansion approach

  • Increase North America share to ~70%
  • Expand Canada with boots on the ground; UK likely via acquisition

Technology/AI strategy

  • Building AI agents and an AI-supported operating model to keep value high and reduce dependency on him
  • Mentioned:
    • A CIO hired to transform tech infrastructure
    • Own software and “plug things together”
    • RTO/training business with 9-year training plans and Australian qualifications for team members

Leadership transitions & “letting go” (ownership vs operation)

CEO succession model

  • Crisis/trigger event:
    • A US board meeting (2 days) “pulled apart” the business like a PE review and created a reality shock
    • The company had too much reliance on him; the CEO resigned the night before
  • Advisory board ultimatum:
    • Step in or step out
  • Temporary stepping in:
    • Found a CEO by promoting an internal leader to COO
    • Later stepped out after ~9 months, then fully transitioned
  • CEO selection criteria:
    • Broad experience (including roles across hundreds of restaurant settings; senior COO/CEO exposure)
    • People-focused background (chief of people → CEO path)
    • Strong organization and work ethic
    • Complements founder weaknesses (e.g., rigid vs “missing policies” tradeoffs)

Founder “car crash” principle

  • Leadership lesson:
    • Don’t keep stepping in and blocking operational mistakes—leaders must learn
  • Shift in his behavior:
    • From frequent intervention → short weekly touchpoints with CEO
    • He prepared questions in advance and deleted ~60% before meetings to focus on what mattered

Key business recommendations & actionable takeaways

  • Treat offshore as a real internal team:
    • Visit at least annually; include in meetings; build shared culture
  • Delegate with process + training, not “direct orders” and assumptions
  • Start offshore with low-friction tasks (calendar/email) and expand capability over time
  • Build systems that preserve standards remotely:
    • Culture plan + engagement plan + EA-driven scheduling/checklists
  • Use one or few key KPIs:
    • North Star = net commencements; supplement with growth dashboard + monthly finance review
  • Focus strategy “deep and narrow”:
    • Build the offering for one dominant client type (here: accounting firms) until systems and differentiation are strong
  • Make CEO/leadership transition a deliberate system:
    • Hire for complementing weaknesses; define control boundaries early
  • For founders:
    • If delegation fails, expect yourself to be the bottleneck
    • If documentation/training aren’t in place, the issue is usually founder design, not staff motivation

Presenters / sources mentioned

  • Nick Sinclair (guest; CEO/founder figure for TOA)
  • Built to Lead (podcast/program context implied)
  • Dean Mitchel (mentioned re: “leverage ladder” / mastermind context)
  • Alex Hormozi (mentioned regarding EA availability/time windows and recruitment expectations)
  • Demartini (referenced for “definition of done” concept)
  • Nick’s coach (unnamed)
  • JC (CEO figure; named only as JC)
  • Ethel (long-term EA)
  • Sheila (example hire / team member)
  • Jamie (host/podcast other person mentioned in conversation)

Rate this summary

Your feedback will help improve summaries.

Improve this summary

Reprocess with a stronger model when the summary feels incomplete or inaccurate.

Pro

Translate summary in another language

Pro

Ask questions to this video

Chat for follow-up questions, clarifications, and source-backed answers.

Coming soon

Share this summary

Original video