Skip to content

Digital product developmentThe right product first.
Then good code.

Website, web app, mobile app, SaaS, e-commerce or custom software. We work out together which one you need, then build it with your sales process and measurement in place.

Need · example

“Our dealers should place orders and see stock in real time.”

  1. Who will use it? · Your team, dealers
  2. Where, replacing what? · Browser

Recommendation · web app

Orders, stock and dealer permissions in one record. First working version in 8-16 weeks.

Six products

Six products.
One engineering standard.

Whichever one we build, the design system, measurement setup, CRM connection, integration layer and ownership handover are standard parts of every project.

01

Website

Customers research and leave an inquiry

6-10 weeks

02

E-commerce

Sales and payment on the site

4-16 weeks

03

SaaS

Software sold by subscription

MVP 8-16 weeks

04

Web app

Your team runs a workflow in the browser

8-16 weeks

05

Mobile app

Used in the field, on a phone

8-16 weeks

06

Custom software

Moving off a legacy system

First phase 8-16 weeks

Under the surface

One visible interface.
Five working layers.

Interface, business rules, access, data and integrations are designed in one plan from day one. An order request passes through five layers and comes back the same way.

01InterfacePlace order
02API and business rulesPOST /orders
03Identity and accessRole: dealer · access: orders
04Dataorder #2481 · stock -4
05IntegrationsERPPaymentCRM

Release and monitoring

Tested in staging first.
Monitored when live.

Every change goes through tests in a staging environment first. Errors in production are caught on the monitoring screen and reported to the team, and the fix goes live the same way.

Every change

Development

Tests and checks

Staging

Users

Live

Automated tests

Accessibility

Speed check

Sales system

The product is never
left on its own.

Every form lands in the CRM with its source, key steps are measured and qualified leads go back to the ad platform as a signal. These connections are built from the first sprint.

examplecompany.com/quote

Request a quote

Full name

Selin K.

Company

Example Logistics

Need

Dealer order portal

Request received

CRM

New inquiry

Source, page and campaign recorded

Analytics

form_submit event

Measured along with the funnel steps

Ad platform

Qualified lead signal

Sent back once sales confirms it

Handover

A weekly demo.
At handover, everything is yours.

Every week you see a working interim version. At handover, the source code, accounts, design files and documents are transferred to your name.

  1. 01 · Discovery
  2. 02 · Information architecture
  3. 03 · Design system
  4. 04 · Development
  5. 05 · Testing
  6. 06 · Launch and handover
Source code Yours
Domain and hosting Yours
Analytics and ad accounts Yours
Design files Yours
Documentation Yours
Training and 30 days of support Yours

BUILD layer

Services in this layer

Short answer

The BUILD layer develops websites, web apps, mobile apps and custom software. The difference: the product is not built on its own but together with the sales process, CRM and measurement setup.

Scope

What is in the BUILD layer?

What you get

  1. 01Corporate websites and premium web experiences
  2. 02Web apps and business software
  3. 03Mobile app MVP and product development
  4. 04E-commerce and configurator systems
  5. 05Integration with existing systems and an API layer

Who it is for

  • Businesses whose website does not bring in customers
  • Teams whose digital product runs disconnected from the sales process
  • Companies that want to develop a new app or product
  • Operations that want to move off a legacy system and work from one record

Problems it solves

  • Every new need creates a separate vendor and a separate data island
  • There is a website, but inquiries are not connected to the CRM or to measurement
  • It is unclear which product is needed, and quotes cannot be compared
  • Code, accounts and documents stay with the developer

Last updated: October 28, 2026

Product choice

Which digital product fits you?

The six product types are built with the same engineering but solve different problems. The right starting point depends on who will use the product and what it will replace.

Comparison of six digital product types
ProductWhen?Example (fictional)Typical timeline
Corporate websiteCustomers research you and you want them to leave an inquiryAn industrial company site whose quote form lands in the CRM6-10 weeks
E-commerceSales and payment will happen on the siteA store connected to shipping and accountingReady-made platform 4-8 weeks, custom 8-16 weeks
Web appYour team or dealers will run a workflow in the browserA panel where quotes, orders and stock are tracked in one recordFirst version 8-16 weeks
Mobile appUsed in the field, on a phone and often through notificationsA field team app for work orders and photo proofFirst version 8-16 weeks
SaaS productYou will sell the software to other companies by subscriptionA multi-tenant booking and billing productMVP 8-16 weeks
Custom softwareMoving off a legacy system, or a process no off-the-shelf package coversA system that replaces macro-heavy Excel files and an old programFirst phase 8-16 weeks

Timelines match the service pages. Final scope and cost are given in writing after discovery. Examples are fictional.

What makes the choice hard is that the need often sits between two products. A system where dealers place orders can look like both a web app and e-commerce. In that case the decision depends on whether payment is taken on the site and who the users are. The first job of the discovery call is to put that distinction in writing.

Fill in the form for discovery

Boundaries

Three distinctions that often get mixed up

The same words are used for different kinds of work. The distinctions below make quotes comparable.

  • Website or web app?

    A website informs visitors and turns them into inquiries. A web app is a tool where logged-in users work every day: they create records, give approvals and track status. If there are user logins and role permissions, it is usually an app.

  • Web app or SaaS?

    A web app solves one business's process. SaaS sells the same software to many customers by subscription. That is why separation of customer data, subscriptions and billing are designed from the start in SaaS.

  • Custom software or an off-the-shelf package?

    If a package covers most of the process, extending the package first is cheaper. Custom software makes sense when the part the package cannot cover is at the center of the work, or when you need to move off a legacy system.

Platform

Ready-made platform or custom development?

For e-commerce and corporate sites, a ready-made platform is often the right start. Custom development comes in when the platform's limits touch the business itself.

Ready-made platform compared with custom development
QuestionReady-made platformCustom development
Time to launchFasterLonger, depending on scope
Starting costLower, may include a monthly license feeHigher, usually no license fee
FlexibilityAs far as the platform allowsDesigned around the business rules
IntegrationReady-made plugins and the platform APIAPI and data model built to the need
OwnershipThe platform account is yours, the code belongs to the platformCode and data are yours, as written in the contract
When does it fit?Standard sales and content flowsBusiness-specific rules such as a configurator, dealer pricing or a custom approval flow

The decision is made in discovery, based on the current process and the growth plan.

Engineering

Which layers do we build a product with?

The visible part of a product is the interface. What makes it work are the layers underneath, and all of them are planned together from day one.

Five thin stacked layers cut vertically by a neon green line, conceptual illustration
Conceptual illustration
  1. 01

    Interface and experience

    User flows, the design system and different screen sizes are designed together.

    DeliverableDesign system.

  2. 02

    API and business rules

    Business rules live in a layer separate from the interface, so the same rules are used by web, mobile and integrations.

    DeliverableAPI contract.

  3. 03

    Identity and access

    Session, role and permission rules are defined in one place. Who can see what and who can change what is written down.

    DeliverableRole table.

  4. 04

    Data model

    Data is modeled around use cases. Backup and restore steps are part of the delivery.

    DeliverableData model.

  5. 05

    Integrations

    External services such as payment, CRM, ERP and accounting are connected with queue and retry logic.

    DeliverableIntegration list.

  6. 06

    Release and monitoring

    Development, staging and production environments are separate. Errors show up on the monitoring screen before users notice them.

    DeliverableRelease and monitoring setup.

Speed benchmark

In Google's Core Web Vitals, the good thresholds are 2.5 seconds for the largest content to appear (LCP), 200 milliseconds for responding to interaction (INP) and 0.1 for visual shift (CLS). They are assessed at the 75th percentile of page loads, separately for mobile and desktop. These thresholds are written down as targets in every project.

Sales system

How does the product connect to the sales process?

A digital product's value is measured by where the demand and data it generates end up. These connections are not added later. They are built from the first sprint.

  • Every form submission lands in the CRM with its source, page and campaign
  • Key steps (form view, submission, qualified lead) are measured as events in analytics
  • Qualified leads are sent back to the ad platform as a conversion signal
  • Cookie and consent preferences are part of the measurement setup
  • The sales team sees each inquiry with the information needed for the first call

Next layers

The CRM process, automations and reporting go deeper in separate layers. The BUILD layer sets up the product side of these connections.

CRM setup

Handover

What stays with you at handover?

A digital product should not stay dependent on the company that built it. Accounts are opened in the business's name from day one.

  • Source code

    All of the code and access to the code repository. Open source and paid components are listed.

  • Domain and hosting

    Domain, server and service accounts are opened in the business's name.

  • Analytics and ad accounts

    The business owns the measurement and ad accounts. The team gets only the access it needs.

  • Design files

    The design system and component library are delivered in editable form.

  • Documentation

    The data model, integrations and release steps are written down.

  • Training and stabilization

    How-to videos and a 30-day stabilization period after launch.

The transfer of economic rights to the source code is written into the contract. Each right being transferred is listed, and the transfer is tied to full payment. Open source and third-party components are subject to their own licenses. This is general information, not legal advice.

Preparation

What to prepare before the discovery call

This list helps the right product become clear in the first call and makes the quote comparable.

  • Who will use the product: customers, your team, dealers or subscriber companies?
  • Which tools is this work done with today, and where is the most time lost?
  • Which systems need to be connected (CRM, ERP, payment, accounting)?
  • Which single measure will you judge success by?
  • In whose name are the accounts of the current site or software?
  • Is there a target launch date, and what does it depend on?

Glossary

Short glossary

Digital product
Any tool a business offers its customers or team through software: a website, an app, a store or an internal system.
MVP
The smallest working version that is enough to test the core value.
API
An interface with written rules through which software systems exchange data.
Design system
A component library where parts such as buttons, cards and forms are defined once and used the same way on every screen.
Staging environment
A copy of production where changes are tried before they go live.
Core Web Vitals
Google's three speed metrics for loading, interactivity and visual stability.
Ownership handover
Delivering code, accounts and documents to the business as written in the contract.

Limits

What we don't promise

  • This page compares six product types. The detailed method for each product is on its own service page.
  • Timeline and cost become clear at the end of discovery. The timelines in the table are starting values.
  • We do not promise traffic, sales or ranking increases. Targets are set together with your data.
  • We do not give legal advice. On ownership and licensing, your contract and legal counsel are what count.

Proof

Products we have built.

Work records that went through this layer. Each record is labeled with its level of evidence.

Quote

Priced by scope.

Websites and e-commerce on ready-made platforms are scoped differently from web and mobile apps, custom e-commerce and custom software. A firm written quote follows discovery, with the cost and deliverables of each phase.

Request a quote

What shapes the quote

  • Product type: website, e-commerce, web or mobile app, SaaS or custom software
  • Integration depth (CRM, payment, ERP)
  • Number of custom features and business rules
  • Content production needs
  • Multilingual requirements

The discovery call is free. Accounts are opened in the business's name from day one.

Process

How it works

A corporate website typically goes live in 6-10 weeks. A web or mobile app MVP takes 8-16 weeks, depending on scope.

  1. Week 1

    Discovery and scope

    Which product, who will use it and how success is measured are written down.

  2. Design

    Information architecture and design system

    Screen flows and the component library are set up.

  3. Every week

    Working demo

    Progress is shown with a working version, not a presentation.

  4. Before launch

    Testing and staging

    Tests, accessibility and speed checks run in the staging environment.

  5. Handover

    Launch and handover

    Accounts, code and documents are handed over and 30 days of stabilization begin.

Assessment request

Product Pre-Assessment

Send the short form. We will get back to you within one business day with first findings on which product to start with.

  • 2-minute form
  • Reply within 1 business day
  • No sales pressure

Prefer to talk instead? Call +90 532 450 75 14.

Frequently asked questions

Frequently asked questions about digital product development

  • In the discovery call we write down who will use the product, which tools the work is done with today and what it will replace. A customer-facing need is usually a website or e-commerce, a team workflow is usually a web or mobile app. The decision is made together, based on that table.

Sources

The official information on this page is based on the sources below. Fees and rules can change, so check the source before you decide.