Where the week goes
Your week, before and after I take over the IT.
By Wednesday the small requests have taken over the calendar. From Thursday I take them over one at a time, and the next week is about the business again.
A short film of one company's week. On Monday the calendar holds seven business meetings and requests start to arrive: a laptop that will not start, a missing signed lease, a legal request waiting nine days, a question about Copilot. By Wednesday eight requests cover the calendar. From Thursday 3DH takes them over one at a time. By Friday six are handled for good. The next Monday the calendar holds eleven business meetings.
What I take over
Whatever your company does, it comes down to six areas.
I set each one up properly, then keep it working.
Workplace
Mail, files, calendars and Teams in Microsoft 365, set up properly and kept that way.
Requests and approvals
Holidays, purchases, legal and admin requests in one place instead of email and chat.
Automation
The copying and sorting people do by hand between inboxes, forms and folders, done automatically.
Security and devices
Laptops encrypted, managed and wipeable.
People and everyday support
New colleagues ready before day one, and one person to call when something breaks: a printer, the Wi-Fi, a lost folder.
Practical AI
AI that reads, sorts and checks documents inside the tools you already use. A person still makes the decision.
Scout, my product for law firms, is one example of this. See Scout.
Cases
Real requests from a company I work with, anonymised. Under each one are a few other places the same problem turns up. I've run companies myself, and I lost hours every week to exactly these things, so I know what they cost.
Workplace
The request: documents spread across Google and Dropbox, every person with their own way of filing.
What I did: everything moved into one Microsoft 365 environment, one login, clear access.
Where else it helps: a shop chain where every manager keeps the price lists on their own laptop, or a manufacturer whose supplier contracts sit in three people's mailboxes.
Requests and approvals
The request: legal requests sent by email and lost.
What I did: one request list, with a notification when something arrives and a status everyone can see.
Where else it helps: holiday requests in a WhatsApp group, or purchases everyone thought someone else had approved.
Automation
The request: thirty shared inboxes sorted by hand every morning.
What I did: 240 tagging rules that sort mail as it arrives, with no errors so far.
Where else it helps: supplier invoices filed by hand, or website orders typed again into the accounting system.
Security and devices
The request: no managed devices at all.
What I did: eleven laptops, one of them a Mac, enrolled, encrypted and wipeable.
Where else it helps: a laptop left in a taxi, or someone who left months ago and can still log in.
People and everyday support
The request: a new lawyer starting on Monday.
What I did: a managed, encrypted laptop with mail, files and tools, ready before they arrived.
Where else it helps: a new sales rep who spends the first week asking for passwords, or seasonal staff who need access in June and shouldn't have it in September.
Practical AI
The request: two versions of a data room to compare.
What I did: a comparison tool the team now runs themselves.
The request: an application to check before it went out.
What I did: a checker that caught a plot entered twice.
Where else it helps: checking a tender against last year's, or a contract against your standard terms. Always inside the tools you already have, and a person still decides.
In their words
What the people using it say.
The legal requests: brilliant. [...] I'm very happy with it. [...] Because nothing gets lost. Before, we sent it by email and it got forgotten.Te wnioski prawne: rewelacja. [...] Ja jestem bardzo z tego zadowolony. [...] Bo nie ginie. Bo tak to na mailu wysyłaliśmy i się zapominało.
Everything's running fine for me. [...] Teams works. Outlook works. [...] It finally works.Mi na razie wszystko hula. [...] Teams działa. Outlook działa. [...] W końcu działa.
I just followed the instructions and did it all myself.Ja tam zgodnie z tą instrukcją wszystko robiłem.
Start with one automation
Before you commit to anything, I automate one task your team does by hand, inside your own Microsoft 365. The first one is on me, so you can see how I work on a problem of your own.
For example:
- Incoming mail sorted and tagged by rules as it arrives.
- Two versions of a document compared, with the differences listed.
- A checker that looks over an application or a list before it goes out.
It's for companies of 20 to 150 people on Microsoft 365: one per company, up to a day of my work. I take on two a month. You give me an account with only the access the task needs, it's removed when I finish, and you keep what I built.
We choose the task in the free 30-minute conversation.
About me
I've run companies myself.
Before I worked in IT, I ran businesses. In Lisbon I owned and ran my own firm. In Warsaw I was general manager of a retail chain that grew from one shop and five people to ten shops and about 150 people, with two acquisitions. After that I built international sales teams selling into Europe, Latin America and the Middle East. In every one of those jobs I lost hours each week to systems that should have just worked.
Before starting 3DH I spent three years at Accenture on the Microsoft account. Now I do that work for companies of 20 to 150 people, and I stay on after the first thing works.
You deal with me, and I do the work myself. When something needs a specialist, I bring one in and tell you who and why.
Microsoft AI Cloud Partner Program member (ISV Success) · Microsoft licensing partner (CSP) through Pax8 · Microsoft Marketplace publisher: Scout, an AI agent for law firms (opens in a new tab)
How it works
It starts with a conversation.
- A free 30-minute conversationYou tell me how the business runs and where the time goes. I won't bring slides or a diagnosis.
- One automation, on meWe pick one task your team does by hand, and I automate it at no cost. Then you decide whether to go further.
- Six months, fixed monthly feeThe scope is written down before anything starts, and there's no hourly billing.
- Ongoing careI stay responsible for what I built and move on to the next thing.
Smaller projects
Not everything needs six months. Some things are a single project: a website, an internal tool, a migration, a checker like the one above. I do those on their own, at a fixed price, with a delivery date. If it leads to more, we can talk about the six months. If it doesn't, you keep what I built and the documentation.
Recent projects: the website of a renewable energy developer in Warsaw, in Polish and English. The website and shop of a skincare brand in Spain. Among other projects developed, landing pages in four languages for HomeTurf, a match-day booking concept for football fans abroad. See the projects
FAQ
Questions owners ask me
What would AI actually do for us?
The reading, sorting and checking nobody wants to do: mail tagged as it arrives, two versions of a document compared, an application checked before it goes out. It works inside the Microsoft tools you already use, and a person still makes the call. If a plain automation does the job better, you get that instead.
We already have an IT person.
That's fine. I work with them. They keep the day-to-day running, and I take on the projects that never get finished: the migration, the security setup, the automation, the AI. They get help, not a replacement.
Do we need Copilot?
Not on day one. Copilot can see everything your people can open, so files and permissions have to be in order first, or it surfaces the wrong things. Once the basics are clean, we test it with a few people and buy more licences only if they use them.
What does it cost?
The first automation is free. After that, it's a fixed monthly fee for six months, agreed in writing before anything starts. There's no hourly billing. It costs less than hiring an IT manager and an AI specialist, and you get one senior person across all of it. Microsoft licences are billed separately and itemised. We talk numbers in the first conversation, once I understand what you need. A project on its own has one price, agreed before it starts.
How do you handle cover and continuity?
You own everything I build. It's documented and handed over whenever you ask. Time off is agreed in advance, and when something needs a specialist or cover, I bring in a partner from the Microsoft partner network and tell you who.
What happens after six months?
You choose. I hand everything back to your team with documentation, or I stay on as your IT and AI function. You pay for a share of my time, not a full-time salary, and when something needs a specialist I bring one in from the Microsoft partner network. Nothing renews automatically, and there's no twelve-month lock-in.