Frequently Asked Questions

Cost depends on scope, integrations and timeline. We agree a fixed build phase and then move into a flexible partnership or retainer model that matches your stage.

It depends on scope. We start with a focused first version, and larger platforms are split into milestones so you can launch, learn and iterate without waiting for everything at once.

Yes. We often embed with in-house teams, take ownership of specific workstreams, or act as the technical partner while your team focuses on market and operations.

Launch is the start, not the finish. We stay involved for scaling, feature growth, infrastructure and ongoing product decisions as a long-term partner.

Web applications, SaaS products, AI applications, MVPs and digital platforms, from a first version to products that keep growing.

No. Many projects start with an idea and a problem worth solving. Discovery and Define turn that into a clear direction before anything is built.

Yes. Most products need more than one discipline, for example strategy, design and development, or a platform with AI features built in.

We do. We take care of secure hosting and deployment, so the product runs in a professionally managed environment.

Not always. Some features work with general models; others get better with your own data. We look at what your product needs before choosing an approach.

By designing for it from the start: clear boundaries, checks on the output and a person in control where decisions matter.

Yes. AI features can often be built into an existing product without rebuilding it.

Yes. Subscription plans, billing and access levels are a common part of the SaaS products we build.

Yes. We build multi-tenant platforms in which each customer's data and settings are kept separate.

That is often the best start. We build a focused first version that can grow with your customers.

When standard tools no longer fit how your business works, or when the process itself is what sets you apart.

Yes. Integrations with existing systems, such as ERP, CRM or accounting software, are a normal part of the work.

Ownership is agreed in the contract before we start, so it is clear from day one.

Only what is needed to test the core idea with real users. We help decide what can wait.

No. We build the first version on a foundation that can grow, so you can keep building on it.

You learn from real use, and we help decide what to build next.

A platform brings several user groups, functions and often a business model together in one product.

Yes. We design the structure so new features and user groups can be added later.

Yes. We plan migrations step by step, so the business can keep running.

It helps. A clear strategy keeps development focused on what creates value.

A shared view of the problem, the users, the priorities and the first version worth building.

Yes. It can stand on its own or lead straight into design and development.

Yes. We build integrations with the job boards, calendars and systems your team already uses.

Not necessarily. Software can extend the tools that work and replace the ones that slow the team down.

Carefully. Candidate data is handled in line with the GDPR, with access limited to the people who need it.

Yes. We design for phones and tablets, so information can be captured and checked on site.

Yes, each with their own access to the information that is relevant to them.

Yes. Integrations with existing planning and financial systems can be part of the build.

That can be designed in, so technicians can keep working where the signal is weak.

Yes. A customer portal can show appointments and progress, and handle changes.

Yes. Completed jobs can flow into your invoicing or accounting software.

Yes. Integrations with ERP, inventory and production systems are a common part of the work.

No. We start from how production works today and digitise the steps that cost the most time.

Yes. Starting with one workflow is often the best way to prove the value before expanding.

With care. Access control, careful data handling and processing in line with the GDPR are designed in from the start.

Yes. Secure portals for appointments, information and follow-up are a typical part of our work in healthcare.

Yes. Where possible, new software connects to the systems the practice already uses.

Yes. A tracking portal lets customers follow orders and shipments without contacting your team.

Yes. Integrations bring order, warehouse and transport data together.

No. New software can sit alongside existing systems and connect them.

Security is part of the design: access control, careful data handling and secure, professionally managed hosting.

Yes. Automation can include approvals and checks, so people stay in control of what matters.

Yes. Secure portals give clients access to their accounts, documents and services.

Yes. AI can help find information and prepare first drafts, with your people checking and deciding.

Yes. A client portal gives clients a structured, secure place for documents and updates.

Usually with the recurring tasks that cost the most time, so the first improvement is felt quickly.

We approach products as partners with a founder's mindset: we look at the business, the users and the long-term direction, not only at the technical brief.

No. We work with founders and with established businesses that want to build a new product or improve an existing one.

Closely. Decisions are made together at every stage, so the product stays connected to the business behind it.

Yes. We design and run products in line with the GDPR.

Your idea, what you know about the problem and the people it is for, and time to talk it through.

No. Sometimes the best outcome is the insight that an idea needs a different direction.

If the problem and the users are already clear, Discovery can be short. It is rarely skipped entirely.

A clear direction: the purpose of the product, its priorities and what the first version should contain.

We decide together. We bring product and technical perspective; you bring the business.

Yes. Define sets a direction, not a fixed plan, and it is revisited as the product learns.

Yes. The experience is shaped and reviewed before it becomes development work.

Yes. We design within your brand, or help shape it where it is still forming.

No. It covers structure, flow and how people move through the product, not only the interface.

Through regular check-ins and working versions, so you see the product take shape.

We choose proven technology that fits the product and can keep developing after launch.

We do. Deployment and hosting are handled securely and professionally managed.

Yes, if you want us to. Growth is about continuing to develop the product together.

From how the product is used and what the business needs, so the next step is based on evidence.

Yes. Our involvement can follow what the product and the business need at each stage.