Request an audit EL

I automate your company’s processes.

I’m Dimitris. With 14 years in software, I map, organise and automate the processes of your business.

Request an audit See a case

For companies of 20–200 people and for agencies. The audit is paid, at a fixed fee.

task queue · Thu 16 Oct 2026 · 08:00–12:30Sample
08:04gmail → softone.orderOrder from email posted in SoftOne, ORD-2026-1094, 14 linesAutomaticok
08:20bank.reconcile23 bank transactions matched to open customer invoicesAutomaticok
09:31rule.stock_check2 lines over available stock. Approved by M. PapadakiHumanok
10:05mydata.invoiceInvoice INV-4472 sent to myDATAAutomaticok
11:12supplier.invoice.matchSupplier invoice matched to purchase order PO-0381Automaticok
expense.approve · 12:24

Expense of €1,840 is waiting for approval from the finance director

Human decision

I connect the tools you already have

Don’t see yours? Ask me
  • SoftOne
  • Epsilon Net
  • myDATA
  • Gmail
  • Google Sheets
  • Excel
  • Outlook
  • Slack
  • Teams
  • Zoom
  • Viber
  • Stripe
  • HubSpot
  • Shopify
  • WooCommerce
  • Airtable
  • Notion
  • n8n
  • OpenAI
  • Oxygen
  • viva.com

Where your team loses time.

Tick what you recognise. On the right you see how it would run, and the list goes with you to the form.

One morning at a wholesale company, after automation.

queue: empty. The day is starting.

AutomaticHuman decision
task queue · Thu 16 Oct 2026 · 08:00–12:30Sample
08:04gmail → softone.orderOrder from email posted in SoftOne, ORD-2026-1094, 14 linesAutomaticok
08:20bank.reconcile23 bank transactions matched to open customer invoicesAutomaticok
09:31rule.stock_check2 lines over available stock. Approved by M. PapadakiHumanok
10:05mydata.invoiceInvoice INV-4472 sent to myDATAAutomaticok
11:12supplier.invoice.matchSupplier invoice matched to purchase order PO-0381Automaticok
12:00ar.reminderPayment reminder sent to 4 customers with overdue invoices, in GreekAutomaticok
12:24expense.approveExpense of €1,840 is waiting for approval from the finance directorHumanwait
38tasks completed
3went through a person
0manual entries

SampleWholesale distribution, 60 people · 16 Oct 2026, 08:00–12:30 · from the execution log

By the end of the morning shift, 38 tasks have completed automatically, 3 went through a person and 0 entries were made by hand. One expense of 1,840 euros is waiting for approval.

Every morning, market news becomes ready-to-edit LinkedIn drafts.

A Greek security systems company. They wanted to write regularly about their market, without someone hunting for news and writing from zero. The system reads, proposes topics to the team inside Slack, and writes a draft only for the ones they approve.

Industry
Security systems
What was automated
LinkedIn and blog content
In production
Since Sep 2026
Tools
n8n, OpenRouter, Slack

BeforeHuman time: about 4 hours per piece

  1. HumanReading the news
  2. HumanChoosing a topic
  3. HumanResearching sources
  4. HumanWriting the post
  5. HumanWriting the article

AfterHuman time: about 15 minutes per piece, for approval and a final check

  1. Automaticrss: news, 08:00
  2. Automaticscrape: full text
  3. Automaticai: relevance
  4. Humanslack: topic approval
  5. Automaticai: post & article
  6. Doneslack: draft for review

Human time per piece:about 4 hours → about 15 minutes

0+

news items a month are read and scored

monthly average, since Sep 2026
0+

topics a month are proposed to the team

monthly average, since Sep 2026
0+

ready drafts a month, post and article

monthly average, since Sep 2026
0%

of runs without an error

last 30 days

What changed

Finding the news, reading it and the first draft are done before anyone starts work. The team opens Slack and finds topics ready for a decision.

What stayed with people

Which topic is worth it and what finally gets published. The team rejects more than half of the topics it reviews. That filter stays with a person on purpose.

The discovery flow in n8n: news from RSS, duplicate removal, AI scoring and a Slack notification
Flow 1 of 3: discovery, filtering and scoringFull size
The writing flow in n8n: collecting sources, AI drafting, a check and delivery to Slack
Flow 3 of 3: writing and delivery to SlackFull size

Another case · 3CO, Netherlands

An online clinic with subscriptions: the back office runs itself.

3CO offers hair loss treatment on a monthly subscription. Behind the site sits an Airtable back office: payments, reminders, invoicing, upsells, abandoned carts and statistics all run automatically. The company’s partners manage the leads and orders assigned to them on their own.

Webflow · Memberstack · Stripe · Airtable

Visit 3co.nl
0+

customers served

0

back-office automations, plus a portal for partners

0+ hours

a week no longer spent on payments and invoices

0

invoices issued by hand

First I see how your team works. Then I propose.

I don’t start from the tool. I start from the process, and if something isn’t worth automating, I’ll tell you.

Mapping

Process audit

1–2 weeks

I talk to the people who do the work and map how it runs today: who does what, in which tool, how often.

DeliverableA map of the process as it is actually run

Organising

Written proposal

up to 5 working days

What is worth automating, what is not, and in which order. With a fixed scope and a fixed price, no fine print.

DeliverableA proposal with scope, timeline and price

Automating

Build

2–6 weeks

I build what we agreed, on the tools you already have, and we test it with real data before handover.

DeliverableLive flows, documentation, team training

Support · optional

Monthly retainer

per month

I watch every run, fix whatever breaks and adjust the flows when your work changes.

DeliverableAn alert on every failure, changes within the month

The audit doesn’t commit you to the build. The proposal is yours, even if you don’t go ahead with me.

Request an audit

Choose where to start.

Most companies start with the audit. If you are a smaller team or an agency, there is a shorter route.

Companies of 20–200 people

Audit, proposal, build

The route I describe above. You start with a paid, fixed-fee audit and decide on the build once you have the written proposal in hand. For teams with many processes, many tools and no documentation.

  • What you get
  • A map of your processes as they run today
  • A written proposal with scope, timeline and a fixed price
  • Live flows, on the tools you already have
  • Documentation and team training
Request an auditNo commitment to the build
Small businesses, 2–15 people

Ready-made automations

No audit and no big project. I set up one tested automation on your tools. The first is the Quote Engine: you say or write what the customer wants, and a costed quote comes out as a PDF.

Ask about the Quote Engine
Agencies

Automations for your clients

I take on the automation part of your projects. You keep the client relationship, I build, document and deliver.

Talk to me about working together
Dimitris Vlachakis

You talk to the person who builds it.

I’m Dimitris Vlachakis. I’ve been writing software for 14 years, and today I use it for one thing: taking repetitive work off teams.

DV Works is a one-person studio. I do the audit myself, write the proposal, build the flows and pick up the phone when something goes wrong. There is no account manager in between. It also means I take on only a few projects at a time.

What I will tell you from the start

  • What is not worth automating, even if you asked for it.
  • What will stay with people, and why.
  • What it takes to keep it working after handover.
Experience
14 years in software development
Based in
Athens, and remote
Languages
Greek, English

Before you write to me.

The questions I hear most often on the first call. If yours is missing, write to me.

Who owns the automations after handover?

You do. They run in your own accounts or on a server you control, with documentation and access for your team. If we stop working together, they keep running as normal.

What happens if a flow breaks?

Every flow I deliver sends an alert when it fails, with the step and the reason. With monthly support, I fix it. Without it, the documentation tells your team what to check first.

Do we have to change tools?

Usually not. I connect the ones you already have. If one does not allow a connection, you will see it written in the audit, before you decide anything about the build.

Do we need a technical person on our side?

No. I need someone who knows the process well and can give me a little time each week while we build. At the end I train the people who will work with the flows.

Do you use AI?

Only where it does something specific: sorting email, extracting data from invoices, a first draft. Most steps in a flow are plain rules, and the decisions stay with people.

What about our data?

It stays in your systems wherever possible. Where a flow sends something to a language model, I tell you exactly what it sends and where, and for sensitive data we avoid it.

How much does it cost?

The audit has a fixed fee that you know before we start. The build has a fixed price per project, set after the audit, once we know exactly what is being built.

Do you work with companies outside Athens?

Yes. The audit is mostly done by video call with a shared screen. For companies in Athens I can also come in person.

request.newfrom: youHuman decision

Tell me where your team loses time.

Two lines are enough. I will reply myself, not with an automatic email.

  1. 1
    You write to meWhich process is on your mind and how many people work on it.
  2. 2
    A short callWe see whether an audit is worth it. If it isn’t, I’ll say so.
  3. 3
    A proposal for the auditIn writing, with scope, duration and fee.

Or write to me directly at dimitrisvlh@gmail.com

I reply within one working day.