Skip to content

How we work

We choose the way we work together based on how many developers you have in-house. It always starts with a call with the engineer who will then lead your project.

Book a call Technology review

We run the whole project

Who it suits

For companies with no IT department of their own, or with one person looking after every system at once.

We take on the scope, the code, the rollout and the server. On your side, one person sets priorities and signs off each stage.

  • We agree the scope with the department that will use the system
  • We maintain the server and keep it updated
  • We keep documentation and access up to date, and both belong to you

A mail sorter for a hotel chain: 95% of emails reach the right hotel and department without reception touching them.

We work inside your team

Who it suits

For companies that have developers but need more hands or experience with a specific technology.

We join your repository, your meetings and your task tracker. We follow your rules, and our code goes through your code review.

  • We step into the existing code without stopping ongoing work
  • We pick up the tasks your team has no time for

Inside the .mdd team we work on integrations with ERP, SAP and microservices.

We oversee your team

Who it suits

For teams that write code on their own, more and more often with AI agents.

We advise on the architecture and review changes before they reach production. We also set the rules for working with agents: what they may change on their own and what a person must approve.

  • A review of every larger change before release
  • Architecture decisions written down in the repository
  • Rules for AI agents fitted to your codebase

How we start

  1. 1

    A call with the engineer

    You talk to the person who will lead the project. You tell them what you want to change, and they ask about the technical details straight away.

  2. 2

    Technology review

    Over a few days we go through your systems, code and servers. You get a report with risks ranked by cost.

    How the review works
  3. 3

    A first small task

    We pick one task whose result you will see in a week or two. By then you know how we work, before you commit a larger budget.

  4. 4

    Ongoing work

    We agree the mode and the rhythm of work. Tasks, hours and decisions sit on one list you can open whenever you like.

You pay for the hours you see in the report

You can tie every hour on the invoice to a specific piece of finished work: a task, a change in the system or a fix you can check yourself. So you always know exactly what you are paying for.

Hours report

  • Order export to ERP6.5 h
  • Stock level fix2 h
  • PHP upgrade on the server3 h
  • Review of the client team's changes1.5 h

Total13 h

Sample report from one week

Care from 300 PLN net a month

A standing agreement to maintain a system that is already live.

  1. Monitoring and updates

    We watch the server and the application, run backups and install security patches.

  2. Help with outages at any hour

    When something stops working, the on-call developer gets straight to the fix, at night and at weekends too.

  3. New features when you need them

    You order fixes and new features when you need them. We bill them by the hours worked, and you see every hour in the monthly report.

What we look after in every project

Code and access in your company's name

The repository, servers, domains and service accounts are set up in your name from day one. You can open the code or hand it to someone else at any time.

Every change reviewed before release

Every change, including code written by AI agents, goes through review by an experienced engineer and through tests. It reaches production only once it passes both.

A backup and a way back

Before every larger release we take a backup and agree how to roll back. If something goes wrong, the system quickly returns to the previous working version.

Documentation that keeps up with the system

We update the system description and deployment instructions with every change. Knowledge about the system stays in the repository, open to everyone on your team.

What you ask us on the first call

“Should we rewrite everything?”
We almost never advise it. First we check which parts of the system work well and can stay. We rewrite what blocks growth or costs more to maintain than a new version would.
“Who fixes it on a Saturday?”
We do. Monitoring alerts us to the outage, and the on-call developer gets straight to the fix.
“Can we start with something small?”
Yes. Start with a technology review or a single task. In a week or two you will see the result and decide what comes next.
“Will the code be ours?”
Yes, from the start of the project. We set up the repository and servers in your company's name, and the documentation grows with the code.
“You work with AI. What about our data?”
We use plans under which model vendors do not train on your data or code. Customer data is processed by open-weight models running on your server or on our VPS.

Technologies we work with

Point at a name to see which projects we use it for.

Websites

Drupal Drupal For institutions and companies with a large multilingual site
WordPress WordPress For companies that want a site their own team edits
Adobe Experience Manager Adobe Experience Manager For corporations already working in the Adobe ecosystem
Astro Astro For companies that want a very fast company website

Let's talk about your systems

You talk to the engineer who will lead the project. Tell us what you want to change and we will suggest the first step.

Book a call Technology review