How we work

From the first call to a working app.

Six steps from first contact to live operation. For each one you know what we do, what you get and what we need from you. Every project is different, so we set the scope, pace and budget individually.

Six steps

What we do and what you get.

01 Getting started

First contact

You fill in a short form: what you need, a rough budget and the type of collaboration. We get back to you and set up an intro call. We don't sell anything on it. We find out what slows you down, what the system must connect to and how you will know the investment has paid off.

What we do

  • We go through how things work today: tools, data, people and the places where work gets stuck.
  • We classify the project: internal system, public product, automation or AI.
  • We tell you whether it makes sense to go ahead, even if not with us.

What you get

  • A written summary of the call.
  • A proposed next step and an indicative project scope.

Your role Time for the intro call and the person who decides on the project.

02 Preparation

Analysis & plan

Instead of a forty-page specification, we start from what you already have: spreadsheets, the current system, exports and emails. When we take over a system from another supplier, we run a technical audit and tell you whether it is worth fixing or rebuilding. The result is a map of your processes and one chosen process that the prototype covers end to end.

What we do

  • We map your processes and the places where data gets retyped between systems.
  • We assess what needs connecting: accounting, CRM, payments, registries and your own systems.
  • We fit the technical approach to your scope and budget.
  • We set success criteria: what the prototype must do for us to continue.

What you get

  • A map of processes and priorities: what now and what in phase two.
  • A technical proposal and a list of connections to your systems.
  • The prototype's scope and price, plus an estimate for the next phases.

Your role Access to data and tools, and meetings with the people who run the process every day.

03 Validation

A prototype on your data

We build a working app on your actual data. It covers one whole process from start to finish, say enquiry → quote → invoice, and we polish the interface only where it matters for the decision. Regular meetings and check-ins show you how the work is progressing.

What we do

  • We import your data or connect to your existing system.
  • We build one complete process, including the most important connection.
  • At regular meetings we go through the running app and make decisions together.

What you get

  • A running prototype that you and your team can try out.
  • A refined scope and price for the live version.
  • What you need to decide: continue, change direction or stop.

Your role Taking part in regular meetings and giving ongoing feedback.

04 After the prototype

Development in stages

We don't throw the prototype away. It becomes the foundation of the live version. We continue in stages, each with a clearly named output. You try every feature in a test version first, and only then does it go live.

What we do

  • Every stage has a named goal and ends with a demo in the test version.
  • Connections to your systems, data transfer, roles and permissions.
  • Automated tests and code review for everything that goes live.
  • We write documentation and guides as we go.

What you get

  • After every stage, a finished feature you can try out.
  • An overview of what is done, what is in progress and what comes next.
  • Access to the source code and the test version throughout.

Your role Attending the demo, trying the test version and setting priorities for the next stage.

05 Launch

Going live

Launch follows a prepared plan: moving live data, training people, publishing in the app stores, monitoring and a fallback plan. For mobile apps we handle App Store and Google Play review. For business systems we keep the old tools running alongside for a while, until the team is comfortable.

What we do

  • Moving live data, with checks that nothing is missing.
  • Team training, video tutorials and user documentation.
  • App Store and Google Play publishing, plus domain, email and monitoring setup.
  • GDPR, consent, backups and an EU region from day one.

What you get

  • A live app on your domains and accounts.
  • An operations guide: what to do when something breaks.
  • A trained team and guides for new colleagues.

Your role A decision on the launch date and people for training.

06 Ongoing

Operations & growth

After launch we stay on the project: we monitor operations, deal with outages, keep the system up to date and add what day-to-day use shows is needed. Our largest projects have grown with us for over a year, adding a module each month that operations asked for. That is how the FoxFix warehouse and community energy in ZEUS Core came about.

What we do

  • Monitoring, outage handling and security updates.
  • Monthly stages with new modules driven by business priorities.
  • AI and automation wherever work is needlessly repeated.

What you get

  • A system that grows with the company without a rewrite.
  • A regular operations overview and a plan for next steps.

Your role Priorities for the next stages and feedback from daily use.

Ways of working

One-off, or long-term.

One-off project

Best for
A website, an enquiry landing page, a single-purpose tool or an app with a clear brief, where nothing fundamental changes after launch.
How it works
We refine scope and price after the prototype. We hand over the project with documentation and a trained team. Maintenance after launch is available if you want it.

E.g. Web Social Lions, Web Pražská energie

Long-term monthly collaboration

Best for
Projects that grow with the business: business systems, platforms, mobile apps and AI automation.
How it works
Every month brings a stage with a named output. A stable team works on it, and you set the priorities. The investment is spread over time and follows what operations actually need.

E.g. FoxFix, ZEUS Core, Slevy a Akce

What working with us looks like

What matters to us when we work together.

See our work

  • One contact, one channel

    You have one person who knows the whole project and a shared channel for quick questions.

  • You see what is happening

    You have access to the test version and the source code throughout. Nothing happens behind closed doors.

  • No lock-in

    Code, accounts and domains are yours. You can continue with another supplier at any time.

  • Decisions based on data

    Before we build something, we test it on your data. Prototype first, specification second.

  • A budget that fits the project

    Every project is different and has a different budget. That is why we discuss the scope and price of each phase up front and adjust them together when the brief changes.

  • Security from the start

    EU servers, roles and permissions, backups, GDPR and clear rules for AI are in place from the first release.

What we need from you

To move fast, we need four things.

  • 01

    Someone who decides

    One contact with the authority to say yes or no. Without them, every decision drags on for weeks.

  • 02

    Access to data and tools

    Exports, access to the current system and accounts for the services the system must connect to.

  • 03

    Regular meetings

    Regular meetings and check-ins over the running app. You know where the project stands, and we know we are building the right thing.

  • 04

    Prompt feedback

    When we show you something, we need to know whether it is right. The faster you reply, the sooner it is done.

Let's start with an intro call.

Fill in a short form. We will get back to you and arrange an intro call.

Send an enquiry