Engagement models
Four ways to work with us
Begin small, prove the approach, then scale when it makes sense. Scope, timing, and terms are agreed in writing.
Most engagements move through these in order. Some start at a defined project. None begin with a commitment you have not chosen.
01 / Start here
A fit conversation
You send a short brief. We reply with questions and a candid view of whether Acadalytics is the right partner, including when it is not.
Best when: You are early, unsure of scope, or comparing options.
- A direct view on feasibility and fit
- Clarifying questions that sharpen your own thinking
- Suggestions for simpler routes where they exist
Commitment: None on either side.
02 / Prove the approach
A pilot on a sample
We run the approach on a small, representative slice of your data or workflow, so you see the method, the checks, and the output quality before committing.
Best when: The data is difficult, the layouts vary, or the stakes of a wrong approach are high.
- Working output on your own material
- A validation report on the sample
- A realistic scope and plan for the full project
Commitment: A short, separately scoped piece of work.
03 / The core model
A defined project
A written scope with deliverables, acceptance criteria, and data-handling terms. You know what you are getting and how you will accept it.
Best when: The outcome is clear and you need it delivered, documented, and handed over.
- Scope, acceptance criteria, and terms in writing
- Working increments reviewed along the way
- Documented handover your team can operate
Commitment: A fixed scope agreed in writing before work begins.
04 / Where the work must keep running
Continuing support
Maintenance, updates, and support for pipelines, tools, and reporting systems that run beyond the first delivery.
Best when: Data refreshes regularly, reporting recurs, or software needs to evolve with the research.
- Defined support scope and how issues are reported
- Dependency, source, and format changes handled
- A named technical owner for the system
Commitment: Defined in the contract. Never assumed.
Working together
What each side brings
What you can expect from us
- A candid view on fit and feasibility, including when the answer is no.
- Scope, acceptance criteria, and data-handling terms in writing.
- Early, working increments instead of a single reveal at the end.
- Validation results reported in full, including failures and limitations.
- Documentation that lets your team operate the work without us.
What we ask of you
- A named person who can answer questions about definitions and data.
- Access to the data, within the permissions we agree.
- Timely feedback at the review points we set together.
- Clarity on what "done" means for your team.
Not sure which model fits?
Most teams do not know at the start. Send a short brief and we will recommend the lightest step that gets you a real answer.