Find your first
useful workflow.
Choose the work. See the scope. Know what happens next.
What HAI can do for your team.
Start with one recurring job. Open a team below to see an example.
Marketing
Less time rebuilding the brief. More consistent messages.
Create from the company you actually are.
Turn approved product knowledge, customer questions and examples of good work into campaign briefs, presentations and content drafts.
Sales
Better preparation. Fewer handovers without context.
Arrive with the whole customer story.
Bring together enquiries, previous offers, commitments and delivery context. Prepare proposals and follow-ups for the sales team to review.
Procurement
Less chasing. Better-informed purchasing decisions.
See the issue before it becomes a delay.
Compare supplier offers, check confirmations against requirements and flag old prices or outstanding commitments.
Finance
A clearer explanation of exceptions and what needs attention.
Connect the numbers to what happened.
Review receivables, payables and cash information alongside the orders, conversations and commitments behind them.
HR
More consistent onboarding. Fewer repeated policy questions.
Make company guidance easier to use.
Prepare onboarding material and answer questions from approved policies. Scope personal records to authorised people.
Legal
Less document hunting. Better-prepared human decisions.
Prepare the material for a better review.
Compare document versions, organise obligations and notice dates, and assemble the supporting correspondence for legal review.
Operations and leadership
Clearer priorities. Fewer commitments lost between teams.
Keep the next step connected to the work.
Bring together delivery risks, open commitments, meeting decisions and responsible people. Configure checks and follow-up around agreed workflows.
Use cases to shape with your team. People remain responsible for publication, hiring, legal and financial decisions.
A clear starting scope.
Start with one recurring workflow on one supported installation. For example: a weekly review of customers, projects and commitments, with sources, open questions, responsible people and suggested next steps.
€3,000
One installation. One recurring workflow. Up to three agreed source sets.
What’s included
- One supported installation on your computer, or on a preconfigured machine purchased separately.
- One main user, plus one person who reviews the results. The reviewer does not get a separate access setup unless agreed.
- Up to three defined source sets that we support, for example selected mail, documents or an agreed system export. Data volume and history are specified in your proposal.
- Initial approved company knowledge and working rules, plus one recurring workflow.
- Two training sessions, a practical guide, acceptance checks and handover.
We agree sources, responsibilities and acceptance criteria before starting. This is the first working scope; further company rollout is planned separately.
€490 / month
Licensed use, supported updates and up to two hours of support each month, including a 30-minute review.
What’s included
- A licence for one agreed installation, including supported product updates.
- Up to two hours in total of support and maintenance each month, including a 30-minute review, checks that your sources still connect and update, small knowledge or rule changes, and help with everyday use.
- Unused hours do not carry over. Additional work and its price are agreed before it begins.
- Fixing defects in what we agreed and delivered costs nothing extra and does not use these hours.
Your proposal names the support contact and service arrangements. This plan does not include a 24/7 service commitment.
Your first 30 days of use and maintenance are included. They start when you accept the working setup. Paid use begins only if you choose to continue after that.
When do we pay, and how is the work accepted?
Pay 50% of the setup fee when agreed access is ready and work starts, and 50% after acceptance. We check five normal cases and two cases with missing or conflicting data, repeat the workflow the next day with a correction, and review sources and access. Acceptance and handover are recorded; silence is not acceptance. Any correction and re-check arrangements are agreed in your proposal. If the agreed result still does not meet the acceptance criteria after those steps, the second 50% is not payable.
Is there an annual commitment?
No. The monthly price is held for 12 months, without a commitment to buy a full year. After choosing paid continuation, you can cancel with 30 days’ notice. Any later price change is notified in advance, with the option not to continue.
What happens if we stop?
Your licence and maintenance end on the agreed expiry terms. You keep any hardware you bought and your company documents, knowledge and rules, and the exit terms include exporting your information. Cancelling does not give a right to keep using HAI Seed indefinitely.
Additional costs and wider rollout
The scope and price of any additional work are agreed before it starts. There are no automatic charges for additional service hours.
- AI services & hardware
- Your AI accounts and usage, and any computer you buy and its maintenance. We review compatible services and the overall budget before agreement.
- Wider company rollout
- Substantial new workflows or source sets, additional roles, installations or computers, custom integrations and large-scale data preparation.
- Actions in connected systems
- Sending messages, making external changes or writing back to company systems require a separately agreed scope and checks.
A small change to the knowledge or rules of your existing workflow may fit within the monthly two hours. Additional work is quoted according to its scope.
Set up around
real work.
We guide the configuration. Your team brings the context and checks the results.
- 1
Agree the first job
Choose a useful workflow, the sources it needs and who can use them.
- 2
Connect and check
Organise company knowledge and test the output with your team.
- 3
Accept and continue
Learn the workflow, agree the handover and keep the knowledge current.
The six setup stages in detail
- 1
Map the company
Work with leadership and relevant process owners to understand the business, key handovers and recurring work. Identify where information is fragmented and what a useful first result looks like.
Typical output: A company context map, priority workflows and named responsibilities.
- 2
Review sources and access
Inventory the selected systems, files and examples. Confirm who administers them, what can be connected and which material must remain restricted.
Typical output: A source and access plan, with gaps and prerequisites made visible.
- 3
Build the knowledge and rules
Organise approved company context, working examples and instructions. Record important terms, decision responsibilities and what each role may use.
Typical output: An initial knowledge foundation and readable operating rules.
- 4
Configure the first workflow
Agree the inputs, expected output, checks and review responsibility. Start with reading, analysis and preparation; scope connected actions separately where needed.
Typical output: A working path from source material to an output your team can assess.
- 5
Validate with the people who use it
Check representative outputs against sources. Test access boundaries, incomplete data and the handover to the next responsible person. Record corrections and re-check the affected work.
Typical output: Reviewed examples, a correction list and an agreed acceptance record.
- 6
Hand over and develop
Show nominated users how to ask, teach, correct and review. Agree support and upkeep, then decide which teams, routines or dedicated machines should follow.
Typical output: A practical operating guide and a scoped expansion plan.
The initial scope and deliverables are agreed in the proposal within the setup package above. Additional departments, bespoke connections and dedicated machines are planned explicitly.
What we need from your team
- 1
An internal sponsor and the right process owners
Someone who can agree priorities, plus the people who know the selected workflows and can review the results.
- 2
A rough map of the information
The systems, files and communications used for those workflows, and who can authorise access.
- 3
A few examples of good work
A proposal, a report, a policy or another approved example that shows the quality and format you expect.
- 4
Your boundaries
Restricted sources, approval responsibilities and actions that must remain with people.
- 5
A result worth checking
One consequential question or recurring job, with a clear description of what a useful output would be.
Your computer or a preconfigured machine
Installation in your environment.
We review the machine and setup requirements, install the HAI environment and help connect the agreed sources with your authorised people.
Delivered ready for company setup.
We prepare the HAI environment on a supplied computer. Account sign-in, company access and acceptance are completed with your team. Hardware is purchased separately. The offer states the equipment, support and handover arrangements.
How to teach HAI and keep it current
Show the standard
Bring your manuals, product information and examples. Explain what makes an answer or document useful in your business.
Confirm the lesson
Review a correction before it becomes a shared method. Agree which roles can use it and which source supports it.
Keep it current
Update the underlying knowledge when your rules or business change. An old decision remains history; current guidance needs current sources.
An example instruction
“Use this proposal as our example. Keep the technical summary short. Flag any delivery date that has not been confirmed.”
The example becomes a working reference. The rule and who may use it are agreed with your team.
As recurring work becomes clear, we can scope dedicated agents, tools, checks and routines around it.
Company knowledge, roles and access
Begin with HAI Seed and one useful workflow. Expand into role-based environments or dedicated machines when your teams need them.
We scope shared knowledge, separate access and coordination for each role.
In a connected deployment, staff can work through familiar channels such as email. Restricted HR, legal and financial records remain within their agreed access scopes.
- Company memory
- Relevant facts linked to customers, projects, people and commitments.
- Reusable methods
- Approved examples, corrections and rules for how work should be done.
- Role-specific work
- Sources, tools and responsibilities configured for each role.
- Controlled expansion
- Additional routines and machines introduced with checks and a named responsible person.
Where the information is stored and processed
Company memory is stored on the deployment machine. Connected AI services process information used for the task under the chosen account and service terms. We explain the intended accounts, sources and support access before connecting company data.
HAI Seed starts with reading, analysis and preparation. Actions that send information or change company systems are separately scoped and checked. Human decisions remain with the responsible people.
A few practical questions.
How long does deployment take?
We agree a phased schedule after reviewing the workflows, sources and access requirements. A first useful workflow and a wider company rollout are different scopes. We make dependencies and acceptance criteria explicit before starting.
What comes with a supplied machine?
The HAI environment is prepared in advance. The proposal specifies hardware, account requirements, support, company-specific setup and what is handed over. Your authorised people complete sign-in and access approvals.
Can people improve it without programming?
They can provide examples, explain rules and review corrections in ordinary language. More involved integrations, access changes and recurring actions are handled as part of the agreed configuration.
We already use AI. What does HAI add?
A maintained company context, agreed working rules and a deployment shaped around your workflows. We look at what you already use and identify where shared knowledge, source checks and continuity would improve the work.
Does everyone need a dedicated machine?
No. HAI can begin on one supported computer. Additional role-based environments or machines are a scoped expansion option for workload and access separation, not a requirement for every employee.
What can HAI Seed do at the start?
The initial Seed environment reads approved information, analyses it and prepares answers and work for review. Company-system changes, outgoing messages and recurring connected actions require separately agreed configuration and validation.
Will HAI replace our existing systems?
Your mail, accounting, CRM and operational systems remain in place. We connect the supported sources or agreed exports needed for the work. The source systems remain the records to check.
How do you keep access appropriate?
We agree who may use each source and what each role may receive or do. Restricted material is scoped separately. Access and workflow checks are part of the deployment; local installation does not mean that AI processing is entirely offline.
Start with useful work.
Bring one important question and the people who understand the work. We will help shape the scope.