How we work, from first call to a system your team runs

Ideolyst delivers AI in four phases: Advise, Prove, Go live and Run. The first three each carry a fixed fee. A build typically reaches production in about three months, with one founder accountable throughout. Your team keeps the code, the weights we train for you and the data, with six months of defect fixes included.

For decision makers planning an AI project, and CTOs checking how delivery, security and handover work.

How long does a custom AI build take?

Typically about three months from the start of Advise, depending on scope and data readiness. Advise takes one to two weeks, Prove three to four weeks, and Go live about two months.

We leadAdvise · Prove · Go live
Your team runs itRun · After
  1. 01 · We lead

    Advise

    1–2 weeks

    Use cases ranked by return, scope fixed in writing

    Fixed fee

  2. 02 · We lead

    Prove

    3–4 weeks

    A working proof of concept on your data, weekly demos

    Fixed fee

  3. 03 · We lead

    Go live

    ~2 months

    In production, on your infrastructure, your team trained

    Fixed fee

  4. 04 · Your team runs it

    Run

    6 months

    Six months included: defects fixed at no cost; changes and new scope are quoted.

    Included

  5. 05 · Your team runs it

    After

    ongoing

    Optional retainer for monitoring and new processes

    Monthly retainer

Each phase is quoted after we understand the workflow, data, integrations and deployment needs. Packaged engines use volume-based pricing.

What we commit to

We stay six months after go-live. Included.

Six months included: defects fixed at no cost; changes and new scope are quoted. Full documentation and training at handover.

One accountable founder on every build.

The person who scopes it signs it off.

Ownership and handover.

Custom-build code, the weights we train for you and your data are handed over in your repositories. Packaged engines are priced by usage; confirm their deliverables and terms separately.

What you keep, and what every build ships with

You keep

  • the code
  • the weights we train for you
  • the data

Ideolyst brings

  • a founder-led team
  • the build, proven on your data
  • six months of defect fixes after go-live

Observability and an eval set

Every model we deliver comes with an evaluation set, a trace of every decision, and alerting, so your team can see when it drifts. We are packaging this layer as a product; it is currently in build.

Security posture

Deployment inside your perimeter, PII masked before any model, internal VAPT before go-live, NDAs as standard. No certification is claimed.

For your CTO

  • deployment inside your perimeter
  • personally identifiable information (PII) masked before any model
  • internal vulnerability assessment and penetration testing (VAPT) before go-live; NDAs as standard
  • open models you can run yourself, full handover of code, weights and data

Straight answers

What does an engagement cost?

Advise is a fixed fee for one to two weeks. Build phases are fixed fee each. Engines are pay-per-use. We quote after understanding your workflow, data and deployment needs.

How long does a typical engagement take?

Typically about three months from the start of Advise, depending on scope and data readiness: Advise one to two weeks; Prove three to four weeks; Go live about two months.

Do you need our data to leave our environment?

No. We build and deploy inside your infrastructure.

Who owns the model and code?

For custom builds, the code, the weights we train for you and your data are handed over to your team. Packaged engines use volume-based pricing; confirm their deliverables and usage terms when scoping the engagement.

What happens after go-live?

Six months included: defects fixed at no cost; changes and new scope are quoted. Documentation and training are included. A retainer after that is optional.

What if AI doesn't fit our process?

We tell you in the advisory report and you pay only that fee.

Bring one problem.

Tell us about one costly process. A founder replies within two working days.

Start with the problem. Agree the right next step together.

For example:

  • a document your team retypes
  • a queue that grows with volume
  • data that can't leave the building