BLOG

How we work. One post at a time.

What working with Cloudwerks actually looks like – from the first conversation to hand-over. Written for owners and managing directors, not for engineers.

  1. The first conversation: what happens in 30 minutes, and what you take away

    Every project at Cloudwerks starts with a free 30-minute conversation with the architect. What happens in it, what to prepare, and what you leave with – even if you never hire us.

    Read more
  2. From bottleneck to fixed price: how a problem becomes a scope

    Between the first conversation and the first line of code there is one document: the written scope. How it comes about, what “finished” means, and what happens to wishes that come up along the way.

    Read more
  3. You know your industry, we know architecture: how we learn your business

    We do not promise industry expertise. We bring a method for turning the knowledge inside your company into a system – and we involve the people who handle the process every day.

    Read more
  4. Eight weeks of working together: what you see – and what we need from you

    The scope is signed – now what? The eight weeks of the MVP Sprint from your side: what you get to see in each phase, when we need your time, and what you do not have to do.

    Read more
  5. Connecting to what already runs: ERP, inventory system, Excel

    New software rarely replaces everything. Usually it has to work with the ERP that has been running for years. How that works without double data entry, what we need from you, and what happens when the ERP has no interface.

    Read more
  6. On your premises or in a data centre? How to decide the hosting question

    Where should the new software run – on your own servers or in a European data centre we set up for you? Five questions that carry the decision, and what applies in both cases.

    Read more
  7. Hand-over and after: why you do not have to depend on us

    The question you should ask every small provider: what if you are no longer around? Our answer is built into the software itself – and into three ways the project can continue after the sprint.

    Read more

The next step is always the same.

A 30-minute architecture call. You describe the bottleneck, you get an assessment of whether and how it can be solved – whether or not you hire us.

30 minutes · free · directly with the architect who builds