Pricing

    Pricing built around what you automate.

    Growy is deployed with you, not downloaded. What it costs depends on the processes in scope, the tools we connect and how much an agent is allowed to do on its own, so the number comes out of a conversation, not a price table.

    Our approach

    No plans. A scope, then a number.

    Every deployment starts from your operations: which process is slowing the business down, what it touches, and what an agent is allowed to decide on its own.

    That is why there is no Basic, Pro and Enterprise here. Two companies of the same size can need very different builds, one has four tools and a clean process, the other has eleven tools, two entities and years of exceptions. We would rather scope it properly than sell you a tier you have to grow out of.

    After the discovery call you get it in writing: what we would automate first, what we would connect, what stays with a person, and what it costs.

    What shapes the quote

    Six things that move the number.

    The same six questions we work through on the call. Nothing here is a hidden extra, it is simply what makes one build bigger than another.

    WHAT WE LOOK ATLIGHTER SCOPELARGER SCOPE
    Processes in scopeOne process, one team, one clear triggerSeveral processes across departments, each with its own exceptions
    Tools to connectFour or five tools with clean, modern APIsEleven tools, one of them legacy or on-premise
    Knowledge to mapA tidy drive and a handful of current SOPsYears of documents across drives, mailboxes and people's heads
    How much the agent decidesDrafts everything, a person approves each timeRuns end to end, with a checkpoint only on exceptions
    Entities, users, languagesOne entity, one language, a single teamMulti-entity, multi-jurisdiction, several languages
    Onboarding & supportStandard onboarding, async supportDedicated onboarding, a named contact, agreed response times

    Most first deployments sit on the left of this table. The point of the call is to work out which columns you are actually in, and to tell you if a smaller start would get you there faster.

    Where teams usually start

    Three shapes of deployment.

    Not packages, just the three patterns we see. Each one is quoted on its own scope.

    Pattern 01

    Prove it on one process

    The most common start: one bottleneck, end to end, in the tools you already use.

    • One workflow, four or five connectors
    • A live agent, not a prototype
    • Reviewed together before it runs unattended

    Pattern 02

    Roll it across departments

    Once one team trusts it, the same pattern is repeated where the work looks similar.

    • Several processes, shared Company Brain
    • Role-scoped access per team
    • Rolled out one process at a time

    Pattern 03

    Run it across entities

    For groups where every entity keeps its own systems and its own rules.

    • Multi-entity, multi-language
    • Per-entity rules and approval limits
    • Consolidated reporting on top

    Next step

    How the discovery call actually goes.

    Thirty minutes, no deck. You describe the bottleneck; we show an agent already solving something close to it, then put the scope in writing.

    A 30-minute call
    No deck, we mostly listen.
    A live demo on your case
    Your workflow, your tools, not a canned script.
    A scoped plan within 48h
    What we would automate first, what we would connect, and what it costs.
    The build starts
    A live agent shaped around your bottleneck, deployed inside your operations in days, not months.

    Already inside real businesses

    The kind of operations Growy already runs.

    A few of the businesses running Growy agents today, anonymised.

    A 100+ store grocery and retail group.

    A bespoke furniture manufacturer with 20+ carpenters.

    A multi-jurisdictional higher education institution.

    A premium aluminium and glazing systems partner.

    Bigbon GroupMicrofluidXLondon & PartnersMy ConvenienceSportAnalisiDomesticaKnights College

    Pricing FAQ

    Before you ask for a quote.

    The questions that come up most often once people notice there is no price list.

    Why is there no price list?
    Because the work is not the same twice. The cost follows the scope: processes, connectors, knowledge to map, how much autonomy the agents get. Publishing a tier would either overcharge the simple builds or under-serve the complex ones.
    What do you need from us to quote?
    One call, usually. Bring the process that hurts most, the tools it touches, and who signs off on what. That is enough to scope a first build and put a number on it.
    Can we start with one process?
    Yes, that is how most deployments start. One bottleneck, running end to end, before anything else is discussed.
    Do we have to replace our tools?
    No. Growy reads from and writes to the tools your team already uses. Nothing is migrated to make it work.
    Who builds the agent: us or Growy?
    Growy does, with you. The planner drafts the agent from what you tell us; the team reviews it and builds it with you. There is no self-service builder to figure out alone.
    How long until something is live?
    A first agent on a scoped process is a matter of days rather than months. Wider rollouts go process by process, so value does not wait for the whole programme.

    Get started

    Still deciding? Let's talk it through.

    Walk us through your use case and we'll tell you honestly what we'd automate first, and what it would cost.

    A 30-minute call
    No deck. We mostly listen.
    A live demo on your case
    Your workflow, your tools. Not a canned script.
    A scoped plan within 48h
    What we'd automate first, and what it costs.
    No code requiredHuman checkpointsYour tools, unchanged

    Prefer a live call?

    Grab a slot that suits you.

    Book a 30-minute call with our team.

    30 minutesVideo callNo prep needed
    See available times

    Opens the calendar over this page. Hosted by Calendly, which sets its own cookies.