CoAchieving

Practical AI.
Personal guidance.

For SMEs with 5 to 50 employees

A different view of your working day

Not more tools.More room.

Not a distant agency

Together with Pieter Haijen

I help SMEs organise their business knowledge and recurring work with practical AI and automation. From the first decision to a solution your team uses.

Explore your free AI opportunity scan

45 minutes · free · directly with Pieter

You get three opportunity areas, one recommended next step and a short summary afterwards.

Call Pieter

Marketing Sales Automation Reporting

Start with the basics

01 / The starting point

Your knowledge is already there.
Make it work together.

A client agreement in your inbox. A way of working in a colleague’s head. Figures in a spreadsheet. Your team has the knowledge, but has to keep piecing it together.

CoAchieving brings the relevant sources and working agreements together in a documented central AI knowledge hub. A shared foundation for your people and the tools they use. The aim: fewer repeated questions, less duplicate entry and clearer follow-up.

  1. Help your team find the right agreement themselves, with its source.

  2. Let marketing, sales and reporting work from the same definitions.

  3. Give AI the context it needs to prepare a useful draft.

  4. Make recurring steps actionable, with clear exceptions and human oversight.

02 / From knowledge to work

How context becomes
a next step.

Choose a work situation. See which sources matter, what gets prepared and where a person decides. An example to explain the principle, not a promise that all your systems connect automatically.

Business memory at work

Fictional, prewritten example · nothing sent or saved

Retain → recall → reflect

Business question

Can we start in November?

Retain

Keep agreements and experiences, with source and date.

recall

Recall the relevant, current context for this question.

Request · fact
Maintenance for two locations.1
Agreement · fact
Intake first; project schedule follows.2
Current limit
6 Oct: capacity not confirmed.3

reflect

Weigh the evidence and draft a proposal with sources.

Draft email · proposal, not a fact

Check capacity before promising a date.

For both locations, let’s scope the work in an intake first.2 I cannot yet confirm a November start: capacity still needs checking.3

Then a person checks the proposal.

Draft · awaiting your review

Selected memory, not model retraining.

No live AI. Changes and approval reset on reload or when switching tabs.

Source 1 · Sales

Prospect’s question

Email · customer request ·

We need maintenance for two locations. Can we start in November? We want a clearly scoped proposal first.

Fictional example source. No customer data or live connection.

Source 2 · Sales

Service agreement

Service sheet · approved ·

We first scope the work in an intake per location. Only then do we confirm the quotation and project schedule. An intake is not a project start.

Fictional example source. No customer data or live connection.

Source 3 · Sales

Initial planning note

Meeting note · initial status ·

Available intake and project capacity have not been confirmed. Do not promise a November start. Check planning before offering a date.

Fictional example source. No customer data or live connection.

Source 4 · Sales

New approved intake plan

Planning decision · approved by planner ·

Approved by the planner on 9 October: an intake slot is available on 12 November, 10:00–11:00, to scope both locations. This replaces the unconfirmed intake capacity in the 6 October note. The customer still needs to accept the slot. The project start is not confirmed; quotation and project planning follow the intake.

Fictional example source. No customer data or live connection.

Source 1 · Marketing

Maintenance service sheet

Offer · approved ·

Our maintenance service provides one contact person and agreements per location. We have no evidence for a fixed time-saving claim.

Fictional example source. No customer data or live connection.

Source 2 · Marketing

Brand voice agreement

Style guide · approved ·

Write directly and humanly. Avoid superlatives and unsupported promises. Close with a question that invites a conversation.

Fictional example source. No customer data or live connection.

Source 3 · Marketing

Lessons from sales calls

Sales notes · observed pattern ·

In recent sales calls, prospects asked who keeps track of maintenance when everyone is busy. This is an observation from those calls, not proof of what all customers want.

Fictional example source. No customer data or live connection.

Source 1 · Reporting

Open quotations

CRM export · dated snapshot ·

Quotation A awaits a response. Quotation B still has an unclear scope. Neither quotation is recorded as closed revenue in this export.

Fictional example source. No customer data or live connection.

Source 2 · Reporting

Project planning

Planning · provisional ·

A provisional start slot is reserved for B. It is not confirmed because the scope is still unclear. Do not present the reservation as a confirmed start.

Fictional example source. No customer data or live connection.

Source 3 · Reporting

Weekly meeting decision

Action list · approved ·

Sales will clarify quotation B’s scope this week. The project lead will only confirm the schedule afterwards. This action is agreed, not yet completed.

Fictional example source. No customer data or live connection.

What underpins a central AI knowledge hub

03 / Building together

Start small.
Build what works.

We start with one task that takes time or attention. Not a list of software. After each step, you decide again whether continuing is worthwhile.

  1. Start here

    A focused first question.

    What does your team keep searching for? What gets entered twice? We choose which problem deserves a measurable first trial.

  2. Define it

    A shared foundation.

    We select sources, define terms and agree who gets access, which exceptions exist and who reviews the outcome.

  3. Build and hand over

    Something your team uses.

    We build, test and hand over. With documentation, guidance and a recovery path, so the solution remains understandable after delivery.

Explore the approach

What stays in your hands

More support.
Your decisions.

  • You choose the sources.

    For each source we define its purpose, access and owner. Only relevant information belongs in the selected workflow.

  • You can see where it comes from.

    Sources, definitions and agreements remain traceable. Missing information stays a question, not an invention.

  • Your team gives approval.

    Communication, publishing and changes have an explicit review point. A prepared draft is not an action taken.

  • The work is handed over to you.

    Documentation, training and an agreed recovery path are part of the solution.

04 / One step at a time

A clear route.
You set the pace.

The AI opportunity scan gives you three opportunity areas and one recommended next step. Before any paid follow-up, you receive a proposal with the goal, scope, price and required input.

View a fictional scan example

Explore the output and boundaries of each phase

Our own practice

This website, too,
starts with context.

For this website, CoAchieving brought together its own marketing knowledge, positioning decisions and boundaries on what it can substantiate. The same principle: establish what is accurate first, then build.

Explore the knowledge workbench

CoAchieving’s own use, not a client case or a claim of results.

The sources

Knowledge and decisions together.

Methods, brand agreements and project decisions were scattered across notes and systems.

The context

One glossary, clear boundaries.

Relevant sources, consistent definitions and excluded claims were documented in advance.

Pieter Haijen

Directly involved, from first question to handover

View Pieter on LinkedIn

Pieter Haijen

You talk to
the person who builds.

I investigate where work gets stuck, build the agreed solution and make sure your team can use it. You do not have to keep explaining your story to a different department.

Sometimes an existing tool is enough. Sometimes a way of working needs to be clearer first. That, too, is a useful outcome of a good conversation.

More about working with Pieter

Before you start

Good questions.
Clear answers.

About your existing tools, your data, what comes next and what happens if a trial does not deliver what you expect.

What happens to our data?

Data minimisation is the default: only data needed for the agreed purpose is considered. CoAchieving puts data processing agreements in place where needed, configures access by role and chooses processing within the European Economic Area where possible. The specific architecture decisions are documented for each project.

Is a central AI knowledge hub just a chatbot?

Chat can be one entry point. The central AI knowledge hub connects selected business knowledge with working agreements, roles and checks, so your team can find information and prepare recurring steps consistently.

Do we stay in control?

Yes. For each workflow we define its owner, which sources are used and where someone must approve. Your team retains decision-making authority and can always pause or adjust an automated step.

Is the goal to replace employees?

The approach is built around a human in the loop. Employees provide context, review output and make the decision. The scan looks for opportunities that strengthen existing work, so people spend less time searching and on recurring preparation.

Will we become dependent on Pieter?

The collaboration is personal, but the solution remains transferable. You receive documentation, guidance, exportable agreements and access to what was built for your organisation. We also document the remaining technical dependencies for each project.

What happens if Pieter is ill or unavailable?

Knowledge does not stay only in Pieter’s head. Decisions, access, ways of working and recovery steps are documented, and where possible the core infrastructure is under your control. For business-critical parts, we explicitly agree continuity and handover in advance.

Why not just use ChatGPT or Copilot?

Those tools can be enough for individual tasks. CoAchieving becomes relevant when you need consistent business context, reliable sources, roles, integrations and quality control. The opportunity scan clarifies which approach fits your work.

Why does this start with a conversation?

A conversation helps avoid automating the wrong step straight away. In 45 minutes we clarify the work problem and the first opportunity. The full scan outcome is described above and on the scan page.

Free AI opportunity scan

Put your first question in a short email.

Pieter replies personally and suggests a time. The scan gives you three opportunity areas and one recommended next step.

Email Pieter about your AI opportunity scan

45 minutes · directly with Pieter · no technical preparation

Prefer to call? 0473 80 38 03