01 / SPEED
Respond and deliver sooner
Enquiries are checked and assigned immediately. Confirmations, internal tasks and next steps no longer wait for someone to notice an inbox.
Service / Independent specialist

/ Business outcomes
01 / SPEED
Enquiries are checked and assigned immediately. Confirmations, internal tasks and next steps no longer wait for someone to notice an inbox.
02 / COST
One reliable flow replaces repeated copy-paste, document preparation and status checking across the team.
03 / QUALITY
Required fields, duplicate checks and consistent rules stop bad data, while failures create a visible alert instead of disappearing silently.
04 / FOCUS
Sales can sell, operations can handle exceptions and specialists can deliver the work customers actually pay for.
/ Examples
These are patterns, not fixed packages. Each trigger, rule and tool is adapted to the way your business already works.
Sales / 01
Before: enquiries sit in email, details are copied to a CRM and follow-up depends on memory.
Flow: validate, enrich, tag by service or location, assign the owner and acknowledge the lead at once.
Business effect
Service / 02
Before: staff confirm appointments, send reminders and ask for missing information one customer at a time.
Flow: calendar events trigger confirmation, preparation instructions, reminders and the post-appointment action.
Business effect
Finance / 03
Before: CRM data is retyped into a proposal, invoice and payment tracker.
Flow: approval creates the documents, updates accounting and synchronises paid or overdue status back to the CRM.
Business effect
Commerce / 04
Before: order details move manually between the store, stock sheet, fulfilment partner and customer email.
Flow: paid orders create fulfilment tasks, update stock, flag exceptions and send accurate status messages.
Business effect
Operations / 05
Before: someone reads PDFs or emails and enters the same fields into a system by hand.
Flow: extract and validate data, then involve a person only when confidence is low or a rule finds an exception.
Business effect
Management / 06
Before: several CSV files are merged every week and the figures are already old when the report is ready.
Flow: agreed events feed a dashboard or scheduled summary with data-quality alerts.
Business effect

Connected work
One hand-off should trigger the next.
Your website, CRM, inbox, calendar, payments and reporting should not behave like separate islands. A reliable integration passes the right data to the next step, records what happened and asks a person only when the case is unusual.
/ AI agents
A modern agent can read an email, file or knowledge base, find current information, call an approved API, return structured data and trigger the next step. The value is not a conversation with a model; it is a task reaching a verifiable result in the CRM, calendar, store or accounting system.
Receives enquiries from the website, email, WhatsApp or another approved channel, identifies intent, asks for missing details, qualifies the lead, creates the CRM deal, suggests a call slot and schedules follow-up. Unusual, high-value or sensitive enquiries go directly to a salesperson with a short summary.
Reads an email, brief, spreadsheet or PDF, extracts requirements and maps them against your services, price book and calculation rules. The output is a structured scope, estimate draft and proposal PDF; prices and unusual terms are released only after an accountable person reviews them.
Answers a normal phone call, transcribes speech, responds from an approved knowledge base, checks availability, creates or moves a booking and sends a confirmation. Complaints and medical, legal or otherwise sensitive topics are transferred to staff according to explicit rules.
Goes beyond quoting FAQs: it locates an order, explains the status, gathers details for an address change or return, opens the request and hands a hard case to a person with the history attached. Editing paid orders, refunding money and other critical actions still require standard checks and permissions.
Classifies incoming messages as a lead, invoice, complaint, supplier or spam; extracts numbers, amounts, dates and attachments; stores the document, creates a task and drafts a reply. Uncertain messages and priority customers route to a person, and every action remains auditable.
Extracts supplier, tax ID, date, line items, total and tax from a PDF, scan or photo, checks mandatory fields and duplicates, then prepares the record for ERP, accounting software or a spreadsheet. A total mismatch or unknown supplier stops automatic import.
Finds companies, tenders, vacancies, competitor changes or other commercial signals against agreed criteria, checks fit and records the source and reason in the CRM. AI can research and prioritise; it does not receive a licence to send uncontrolled outreach and damage domain reputation.
Answers questions such as “what did we promise this customer?”, “where is the contract?” or “which invoices are overdue?” by retrieving only authorised data from CRM, email, documents and databases. Answers cite sources, respect the employee's access and never replace the financial or legal system of record.

A practical starting point
Start small. Prove the value. Then automate more.
The first release does not need to transform the whole company. It should remove one visible bottleneck, survive real exceptions and return enough time or speed to justify the next investment.
/ Worked examples
These examples show what measurable improvement could look like across different workflows. Replace the volumes, time and hourly cost with your own numbers to see which process could create the most value.
Sales / lead routing
≤5 min
target time to acknowledgement and owner assignment
€400 / mo
admin capacity returned at €30 per hour
A team receives 80 enquiries each month and spends about 12 minutes checking, tagging, copying and assigning each one. Validation and routing reduce the manual part to roughly two minutes for exceptions and review.
80 leads × 10 min saved = 13.3 h × €30 = €400 / month
Finance / invoice intake
25 h / mo
manual entry and checking removed from the monthly queue
€750 / mo
capacity returned at €30 per hour
At 250 supplier invoices per month, extracting fields, checking totals and preparing the accounting record can conservatively remove six manual minutes per document while mismatches still go to a person.
250 invoices × 6 min saved = 25 h × €30 = €750 / month
Service / booking reminders
6 / mo
additional attended appointments if no-shows fall by four points
€480 / mo
contribution retained at €75 per attended appointment
For 160 monthly bookings, confirmations, preparation instructions and timed reminders are modelled against a four-percentage-point reduction in no-shows. The real baseline and margin decide whether this case is attractive.
160 bookings × 4% recovered × €75 = €480 / month
Management / reporting
12 h / mo
specialist time returned from assembling four reports
€540 / mo
capacity returned at €45 per specialist hour
When a specialist spends three hours merging exports and checking the same figures for each weekly report, a scheduled data flow can prepare the standard view and leave only anomalies and commentary for review.
4 reports × 3 h saved × €45 = €540 / month
Possible outcomes based on the assumptions shown. Actual results depend on process volume, baseline quality, adoption and exception rate.
/ Prioritisation
I score candidate workflows against the same practical questions before recommending a build.
A ten-minute task repeated fifty times a week is a stronger candidate than a frustrating task that appears twice a year.
We include staff time, waiting time, rework, missed follow-up and the cost of preventable mistakes — not only mouse clicks.
Clear inputs, decisions and outputs make reliable automation possible. If the process is unclear, I simplify it before connecting tools.
We automate one complete path with monitoring and an exception route. That creates value sooner and produces evidence for the next decision.
/ Cost control
Removing an unnecessary approval or duplicate field is cheaper than automating it. The workflow is simplified before technology is added.
If your existing CRM and email tool already connect reliably, I use that path. It avoids extra software, custom code and maintenance.
Workflow platforms are useful when several standard tools must exchange data. Flows live in your account, with understandable steps, logs and error notifications.
I build against REST or GraphQL APIs and webhooks when validation, transformation, scale or reliability requirements exceed no-code options. The custom part stays as small as practical.
/ Delivery
Show me the repeated task, who performs it and where it gets stuck. I will tell you whether it looks worth automating and what information is needed next.
I map triggers, systems, decisions, exceptions and current effort. Together we choose the workflow with the clearest combination of impact and feasibility.
You receive the proposed flow, systems involved, ownership, acceptance criteria, implementation price, expected running costs and assumptions.
I implement in your accounts, test normal and failure paths with representative data, and launch with monitoring rather than hoping every API always works.
Your team gets documentation and a walkthrough. We compare the result with the baseline, fix friction and only then decide whether another workflow is worth doing.
12+
years in web development
120+
projects launched
24h
typical first reply

Control before action
AI interprets. Rules decide. People stay in control.
Flexible interpretation is useful at the edge of a process. Before anything changes in the CRM, accounting system or customer record, ordinary code checks the result against permissions, limits and business rules.
/ Architecture
Production automation is not built by giving a model access to everything. Every action has an explicit contract, allowed data, permissions, limits and a route back to a person.
A form, email, call, new file or order change is received by ordinary code. It identifies the organisation and user, removes irrelevant data and gives the agent only the context and tools required for this task.
The model classifies intent, extracts fields or proposes the next step in a defined JSON schema. Free-form text never becomes a direct command to the CRM, payment system or database.
Code checks types, required fields, permissions, price ranges, customer existence, duplicates, order status and limits. Low confidence, a conflict or an unknown value sends the case to a review queue.
An official API is preferred. MCP can expose a narrow set of described tools. When no API exists, browser automation runs in a controlled environment with a separate role, allowed screens and a stop condition if the interface changes.
Input, rule version, decision, tool call and result are recorded without unnecessary personal data. Money, deletion, publishing, access rights and unusual customer commitments may require human approval before an irreversible action.
/ Deliverables
Your organisation owns the workflow, connected accounts and credentials from day one. The system does not depend on my private automation account.
Triggers, fields, rules, destinations, exception paths and pause procedures are written down so the logic is not trapped in one person's head.
Bad input is caught, temporary failures can retry and unresolved problems notify a responsible person with enough context to act.
You know which subscriptions and usage fees the workflow depends on and which costs may change as volume grows.
The original effort and target outcome are recorded, making it possible to assess whether the workflow delivered value before expanding the programme.
You work with the person mapping, building and testing the integration — no agency hand-off between sales, project management and development.
/ Honest check
The process is unclear: automation only scales confusion. Define the correct outcome before encoding it.
The task is rare: a documented checklist may cost less than building and maintaining an integration.
The rules change every week: automate the stable core and keep changing decisions manual until they settle.
Human judgement is the product: software can prepare sensitive communication or negotiation, but a person remains accountable.
If automation is unlikely to return its cost, I will say so during the first conversation rather than sell a workflow the business does not need.
Describe one repetitive process, how often it happens and which tools are involved. I will reply within 24 hours with the questions needed to assess the quickest useful win. The first 20-minute call is free and there is no obligation to build.
Start with a stable task that happens often, consumes meaningful team time and has a clear trigger and result. Lead routing, booking reminders, invoice preparation, document intake and recurring reporting are common first wins. During the initial call I compare frequency, time per run, error cost and implementation effort so we can choose the workflow with the strongest practical return rather than the most fashionable technology.
We establish a simple baseline before building: how often the task occurs, how many minutes it takes, who performs it, what errors or delays cost, and what the tools will cost each month. The proposal then shows the manual steps removed, the expected operating cost and the assumptions behind the estimate. You can compare the build cost with the capacity returned to the business before approving the work.
One complete workflow — routing enquiries, booking reminders, invoice preparation — typically starts at €1,500 with a fixed scope. Connecting several processes into one data flow between CRM, payments and reporting starts at €5,000. Most flows then run for months untouched, so a monthly retainer is optional: I handle changes on request, or from €300 per month if you want ongoing support. Tool subscriptions are counted separately — an n8n or Make plan, your CRM, your email tool — and I give you the expected monthly figure before we start, choosing the cheapest option that works reliably. Scope, price and acceptance criteria are fixed in writing before any work begins, and you pay a developer directly with no agency markup.
Whenever possible, the ones you already use: HubSpot, Pipedrive and other CRMs, Stripe and PayPal, Google Workspace, calendars and booking tools, invoicing and accounting software, WordPress and headless CMS platforms, Google Sheets, Airtable, Notion and internal databases. I use native integrations first, then n8n or Make, and custom REST or GraphQL integrations when off-the-shelf options are not reliable enough.
A focused workflow can often be mapped, built and tested in days rather than months. The exact timing depends on API access, data quality, exception rules and the number of systems involved. I begin with one bounded process so the business can see value before expanding automation further.
Every flow is documented: what triggers it, what data moves where, which rules apply and what happens on failure. If you replace a tool, the affected steps can be changed without rediscovering the whole process. The accounts, workflows and credentials remain under your control, so there is no dependency on a private setup only I can access.
Only where it is useful: classifying enquiries, extracting data from documents, summarising long threads or drafting replies for human approval. Deterministic actions such as creating a CRM record, calculating a total or issuing an invoice stay rule-based. When AI is involved, I define which data it can see, confidence and fallback rules, and where human approval is required.
Sometimes, through controlled browser or computer-use automation: the agent opens the interface, locates the record and completes the form like a user. This is a fallback for legacy CRMs, ERPs and supplier portals. I check exports, imports, APIs and webhooks first; interface control is reserved for stable, narrow workflows with a separate account, action logs, limits and a stop condition when the screen is unexpected.
The workflows run in accounts you own, with credentials stored in your environment. I minimise the data each service receives, document where customer information moves and design with GDPR constraints in mind. Access, error logs and retention can be reviewed as part of the implementation.
Related / Services
E-commerce automation for online stores: supplier imports, catalogue data, product content, translations, SEO, feeds, stock, orders and returns in one controlled pipeline.
E-commerce Automation →02Turn an AI-built prototype from Lovable, v0, Bolt or Cursor into a real, secure, production-ready product — payments, auth, data, tests and deployment done properly.
AI Prototype to Production →03Analytics and conversion tracking for websites, stores and SaaS products: GA4, GTM, consent, advertising pixels, business events and verified reporting you can trust.
Analytics & Conversion Tracking →