Skip to content
Design Partners

Prove the scenarios the market has not solved yet — with us.

A Design Partner brings a scenario we do not yet handle well, and works with us to prove it. We choose scenarios that make Complifly better for similar customers. Being a Design Partner does not oblige Complifly to build anything.

Who we are looking for

A representative scenario, not a unique one.

  • An ERP, a document type, a multi-GSTIN structure or an industry case that we do not yet handle well.
  • A scenario that other companies are likely to share, so that proving it helps them too.
  • A named product owner on your side who can attend the working sessions.

What each side does

You

  • Name a product owner.
  • Agree three to five scenarios to be proven, written down before go-live.
  • Attend the working sessions and the reviews.
  • Let our consultant review your ERP mapping with you.

Complifly

  • Gives you direct access to the product team and a named consultant.
  • Prioritises proving your scenarios.
  • Reviews your set-up with you at agreed intervals.
  • Agrees in writing, before onboarding, how findings from your scenario may be used.

Governance

  1. Working sessions

    Fortnightly during onboarding, then monthly, with your product owner, our product team and your consultant. Decisions and a change list come out of each.

  2. Executive reviews

    Quarterly, with a senior person from your finance or compliance team and from Complifly management.

  3. Exit review

    At twelve months, everyone decides: continue, convert to a standard engagement, or end.

How findings from your scenario may be used

Anonymised findings from your scenario may be used in Complifly’s product decisions. Your organisation is not named or identified when they are. We confirm this with you in writing before onboarding starts, and you acknowledge it when you apply.

What we do not promise

No roadmap commitments, no custom build that has no value beyond you, and no exclusivity unless it is agreed in a contract.

How it works

  1. Apply with your scenario

    Describe the scenario, why it is representative, and who your product owner is.

  2. We review the fit

    Product and pre-sales look at whether the scenario is real, representative and worth proving.

  3. We agree the scenarios in writing

    Three to five, and how we will know each is proven.

  4. Onboarding and working sessions begin

    The same onboarding path as any customer, plus the working sessions.