What people ask before they start

Teams that need to put their operation in order and standardise it, and that have someone able to decide. We check the fit works both ways in the diagnosis before either side commits.

It depends on the size of the system and the number of automations, or on the size of the site. After the diagnosis you get a proposal with fixed scope and fixed price. No open hours, no surprises halfway through.

Yes. That is where it shows fastest: the fewer people you have, the more expensive repetitive manual work becomes.

Because it holds relational databases, documentation and daily work in the same place, and your team can change it without waiting on a developer. If your case calls for something else, we will say so in the diagnosis. We do not force Notion where it does not fit.

The workspace runs on Notion and the automations on Make or n8n, so those are the tools you keep. They are cheap, standard and your data can be exported. What we write from scratch, stores, admin panels and websites, has no platform underneath it at all and is fully yours.

That is the most common starting point. We audit what exists, keep what works and rebuild the structure underneath. Starting from zero is rarely necessary.

That is the real risk in any project like this, which is why training and post launch adjustment are part of the delivery and not an upsell. We design with the people who will use it, not only with leadership.

Only to what you decide, with scoped permissions. We define together what each agent can read and what it is allowed to do, and we document it.

A landing page is two weeks and a full store four to six, counted from the day the scope is closed and not from the first call. What moves that date is almost always content: photos, product data and who signs off on the copy.

We write it and you correct it. Most weak sites are a copy problem wearing a design costume, so we would rather write it than receive it. If you already have a voice you want kept, we work from it.

You do, from day one: the repository, the domain, the analytics and the content. Nothing is licensed to you and nothing stops working if we stop working together. It is standard code, so any developer can pick it up. There is no private framework of ours in the middle.

Yes. Products, prices, orders and posts are yours to change from an admin panel built for the way you work. Where a site needs editable pages we add a CMS, but we do not install one so that somebody can edit a headline once a year.