Skip to content
dvnt.io

CLIENT PORTAL · PANEL · INTERNAL SYSTEM

Web application development for businesses

We build web applications that fit the way your company works: a client portal, an order handling system, a CRM, a management dashboard. When Excel and off-the-shelf tools stop keeping up with the company, the application brings the data into one place and takes manual work off the team.

WHEN IT'S WORTH IT - 4 SIGNALS

When a web application pays for itself faster than an off-the-shelf SaaS

A custom application pays for itself faster than off-the-shelf SaaS when you recognise at least two of four signals: the SaaS forces you to change your process, people rather than APIs move data between systems, B2B customers expect self-service, and management decides on late Excel reports. That is the time for an architecture conversation.

  • THE PROCESS DOES NOT FIT

    An off-the-shelf tool forces a change of process

    You bought a ready-made CRM or an industry system, and the team complains. The tool does not fit the way you work, so Excel comes back through the back door or the process bends to fit the tool.

    How to recognise it

    • Workarounds instead of features
    • Half of the features unused because they do not fit your industry
    • The team says "it's easier in Excel"
    • Fees grow for extra tools that patch the gaps

    The application mirrors your process: one database, one login, one set of rules.

  • DATA IN MANY PLACES

    People carry the data between systems

    An order from the shop retyped into accounting, a lead from a form into the CRM, an invoice into the management report. Every retyping takes minutes and risks a mistake.

    How to recognise it

    • Data travels in Excel, e-mails and PDFs
    • Someone in the office spends a large part of the day copying data
    • Reports are late because the data has to be gathered first
    • A new client has to be set up in several systems separately

    The application connects the systems you already have: data flows on its own and reports build themselves.

  • CUSTOMER SELF-SERVICE

    Clients ask for status, the team answers by e-mail

    Business clients want to check an order, download an invoice or file a complaint at any time. When everything goes by e-mail, answers take longer, costs grow, and a competitor with a client portal looks more professional.

    How to recognise it

    • Clients ask "do you have a client portal?"
    • The service team keeps answering the same status questions
    • A complaint takes several e-mails back and forth
    • Competitors in your industry already have a client portal

    A client portal takes repetitive questions off the team and works around the clock.

  • DECISIONS ON DATA

    Management decisions based on late Excel reports

    The management report is put together by hand from several systems and is ready after a few days. Decisions are made on week-old data.

    How to recognise it

    • Reports prepared by hand in Excel
    • "How are we doing?" takes e-mails to several departments
    • Data from several systems combined from scratch every time
    • The analyst spends most of the time on repetitive work

    A dashboard shows data from the CRM, accounting and warehouse as it happens and warns when something is off.

// 4 SCENARIOS · PICK A TYPE

What specifically are we building

Four kinds of web applications we build for companies most often.

  • SAAS

    SaaS application — from MVP to product

    For companies building their own subscription product, or an application used by many departments or clients, each on their own data.

    What it covers

    • Client data kept apart from day one
    • Subscriptions and recurring payments
    • Login with two-step verification
    • A version under partners' brands, if you need one

    You grow the product in stages over the years, without rewriting it from scratch.

    Typical project: 8-16 weeks.

  • DASHBOARD

    Management dashboard with live data

    For management and operations teams who want to see how the company is doing without waiting for a report.

    What it covers

    • Data from the CRM, accounting, warehouse and production in one place
    • Details in one click instead of manual Excel reports
    • Alerts when something is off

    The analyst stops assembling reports by hand and starts analysing them.

    Typical project: 6-12 weeks.

  • CRM

    A CRM that fits your industry

    When Pipedrive, HubSpot and similar tools do not fit the way you sell, e.g. in healthcare, finance, manufacturing or logistics.

    What it covers

    • Your own sales stages and way of pricing offers
    • One database and one login for the whole team
    • Connection to the systems you already use

    Typical project: 8-14 weeks.

  • B2B PORTAL

    A portal for partners and distributors

    For companies selling through agents, distributors or regional partners.

    What it covers

    • Each partner sees only their own orders, margins and materials
    • A version under the partner's brand, if you need one
    • Support for several regions

    Typical project: 12-20 weeks.

WHAT YOU GET · 4 THINGS INCLUDED

What you get in the price of the application

Every web application, whether a SaaS, a client portal, a dashboard or a CRM, comes with four things as standard. No surcharges, no premium packages.

  • DESIGNED FOR YOUR PROCESS

    An application that fits how the team works

    Many applications copy the look of popular software. They look modern but do not fit how the company works, and people click more instead of less.

    How we do it

    • Before designing, we talk to the future users: what they do, how often and how long it takes
    • We test a clickable prototype with them before any code is written
    • After launch we improve the key paths based on data

    People start using the application quickly, without months of training.

  • MONITORING AND ALERTS

    You know about a problem before the user does

    Your team uses a business application every day, so every error costs: a lost order, a wrong calculation, missing data.

    What comes as standard

    • Error tracking, together with what the user did just before
    • Uptime checks and an alert when the application stops working
    • Data on how people use the application
    • Performance tracking and warnings about unusual behaviour

    We tell you about an error, not the other way round.

  • ARCHITECTURE FOR YEARS

    An application you add features to instead of rewriting

    A business application lives for years, so we build it for growth, not just a quick start.

    What it gives you

    • You can add an admin panel or a mobile app without rewriting everything
    • We catch errors before release, not with your users
    • Database changes go in a controlled way, with no risk to the data
    • Another client or branch is a matter of settings, not a rebuild

    Growing it years later means adding features, not months of reworking the system.

  • SECURITY AS STANDARD

    Security the user does not see, but it is there

    The application holds your clients' data, and a leak is a legal (GDPR), reputational and operational problem.

    What comes as standard

    • Login with two-step verification, passwordless or through a company account
    • Role-based permissions: everyone sees only what they should
    • Encryption of data at rest and in transit
    • Protection against common attacks and password guessing
    • Change history: who changed what and when

    The application passes a large client's security audit, and your compliance team gets the documentation.

STACK - 4 LAYERS OF ARCHITECTURE

Technology stack for web applications

By default we build web applications in Next.js and TypeScript on PostgreSQL, with editable content managed in Payload CMS; we choose a different stack when the project requires it or your company already has its own ecosystem. Below are the four layers (frontend, backend, auth, infrastructure) with the most common choices and decision criteria.

  • FRONTEND

    Next.js + React Server Components + Tailwind

    Default frontend for web applications can be: Next.js with App Router and React Server Components. Tailwind CSS + shadcn/ui as component library. React Hook Form + Zod for form validation.

    Why this stack

    • Next.js App Router - server components reduce JavaScript bundle 30-60% vs pure client React, better LCP/TTI
    • Tailwind + shadcn/ui - design tokens as CSS variables, component library copy-paste (not node_modules dependency)
    • Zod validation - single source of truth for types frontend + backend + database

    When to withdraw

    • Vue / Nuxt - when the customer already has the Vue ecosystem in-house
    • Astro - for content-heavy applications with minimal interactivity (documentation, information portal)
    • Angular - enterprise customers with existing Angular database

    In 90% of dvnt web application projects: next.js. The remaining 10% depends on the client.

  • BACKEND AND DATABASE

    Node.js + TypeScript + PostgreSQL + Prisma

    Backend for web applications can be implemented based on: Next.js API Routes (serverless functions) or dedicated Hono/Fastify for high-throughput APIs. Database: PostgreSQL with Prisma ORM. Background jobs: BullMQ + Redis (when needed) or Inngest (serverless background tasks).

    Why PostgreSQL

    • ACID transactions - consistent data even on failures
    • JSONB columns - flexibility NoSQL, but in a relational database
    • Row-level security - multi-tenancy ready without application-layer hacks
    • Production proven - since 1996, used by Stripe, Reddit, Instagram

    Why Prisma

    • Type-safe queries - error in queries caught compile-time
    • Auto-generated migrations with schema diff
    • Studio (GUI for base) in development, prod-safe in production

    Alternatives considered: Drizzle (lighter ORM, edge-deployment), TypeORM (legacy projects), raw SQL (when Prisma constraint).

  • AUTH AND MULTI-TENANCY

    Auth selected for the application's business model

    Auth has no single default in web applications - it depends on the business model:

    Single-tenant (one company, many employees)

    • NextAuth/Auth.js + email magic links or OAuth (Google, Microsoft) - simplest, zero vendor lock-in
    • Role-based access control from the base (RBAC) - admin/user/viewer

    Multi-tenant SaaS (multiple clients, each with their own workspace)

    • Clerk or WorkOS - turnkey solutions with multi-org support, SSO, SCIM provisioning
    • Custom solution on NextAuth (when budget tight or specific requirements)

    B2B portal with partners

    • SSO (Single Sign-On) from the client system - SAML 2.0 or OAuth
    • Provisioning automatic from HR of the customer's system

    Auth security baseline (each application)

    • Multi-factor 2FA optional for user
    • Rate limiting on login endpoints (brute-force protection)
    • Audit log of each login (GDPR compliance)
    • Sessions with secure HttpOnly cookies
  • INFRASTRUCTURE AND DEPLOYMENT

    Infrastructure selected for scale and requirements

    The most common dvnt web application deployment scenarios:

    VPS - 80% of our client projects

    • VPS - cost PLN 80-200/month.
    • Docker containers, Traefik load balancer, automated SSL
    • Database PostgreSQL on the same VPS or separate (depending on scale)
    • Backup daily + retention 30 days

    Cloud (AWS / GCP / Azure) - 15% of projects

    • When the customer already has a cloud ecosystem (Azure AD, AWS S3, GCP BigQuery)
    • Serverless architecture (Lambda/Cloud Functions) for event-driven workflows
    • Managed database (RDS/CloudSQL) - higher cost, but managed by cloud provider

    Vercel + Neon/Supabase - 5% of projects

    • Global edge network - when an app has users on 3+ continents
    • Zero DevOps overhead - automated preview deployments per PR
    • Trade-off: cost increases non-linearly with scale (>200k MAU)

    CI/CD any application

    • GitHub Actions - automated tests + build + deploy for staging after each merge
    • Production release manual after code review + acceptance testing

// PROCESS · 5 STAGES

From consultation to production - in stages

Every application goes through the same five stages. The time depends on the scope, and the key decisions are made at the start, not after the fact.

  1. 1-2 weeks · free

    Consultation

    We start with a 15-minute consultation, and in 1-2 further calls we learn the processes the application should support and the systems you already use. We check whether a custom application makes sense or an off-the-shelf tool is enough.

    What you get

    • A recommendation: build or buy
    • An initial technical plan with the reasons for each decision
  2. 2-3 weeks · paid stage

    Analysis and specification

    We talk to the future users and describe how the application should work.

    What you get

    • The data model
    • A description of the integrations with your systems
    • Access and security rules
    • Requirements you accept the application against
  3. 2-4 weeks

    Design and prototype

    We design the screens and test a clickable prototype with users before any code is written. Most usability problems show up then, not after launch.

    What you get

    • A clickable prototype tested with users
    • A visual design in line with your brand, if you have one
  4. 4-12 weeks · two-week stages

    Build and test version

    We show progress every two weeks. You have a test version from the start, so you give feedback as we go, not only at acceptance.

    What you get

    • The key journeys and integrations first, extras after launch
    • Automated tests of the key features
    • A preview of every change before it goes live
  5. Launch + 30 days of stabilisation

    Launch and stabilisation

    We launch the application with error and uptime monitoring, hand over the documentation and for 30 days fix, at no extra cost, whatever comes up in daily use.

    After stabilisation you choose

    • End of cooperation, the code stays with you
    • Ongoing technical care
    • Further features

OUR WORK

What we have built

Systems that run in production — each with a link to the details.

  • RADAR PRZETARGÓW

    BZP, TED and Baza Konkurencyjności in one feed

    Every hour it pulls notices from three registers — BZP (Polish public procurement bulletin), TED (EU tenders) and Baza Konkurencyjności (Polish EU-funds tender database) — and sends the relevant ones to Discord and by e-mail.

  • DOMYKO

    Client portal for accounting firms

    Missing documents, e-mail and SMS reminders, invoices from KSeF — under the firm's own brand.

  • DVN LINKS

    Link shortener with QR codes

    From a tool for a single user to a SaaS platform with plans and payments.

PRICING · 3 VARIANTS

How much does a web application cost

The prices below are a starting point. On a call we advise what really has to go into the application and look for the solution that suits your company best. You get the final quote once the scope is agreed.

  • SMALL · 6-8 WEEKS

    from PLN 10,000

    For whom: one module and 1-2 kinds of users, e.g. a simple client portal or an internal tool.

    A simple application can be built as a module of our platform, which makes it cheaper and faster.

  • MEDIUM · 8-12 WEEKS

    from PLN 60,000

    For whom: several user roles and integrations with the CRM, accounting or payments.

  • COMPLEX · 12-20+ WEEKS

    from PLN 120,000

    For whom: a SaaS product for many companies, extended permissions, many integrations and compliance requirements.

What the project price does not include

Besides the cost of building there are running costs: hosting, fees for external services (payments, SMS, AI), the domain, and marketing and content. We list all of them in the quote, so you know the full cost before we start.

// WHAT SETS US APART · 3 THINGS

3 things we do differently in web applications

Whatever the size of the project, these three things are included in every application.

  • READY FOR MORE CLIENTS

    A second company, brand or region without a rebuild

    We build the application so it can serve many clients from the start, even if there is only one at launch. When a second brand, branch or partner comes years later, it is a change of settings, not months of reworking the system.

    What it gives you

    • Each client's data kept apart at the database level
    • Their own logo, colours and settings for each client
    • A version under a partner's brand in weeks, not months
  • READY TO WORK FROM DAY ONE

    No nervous launch and no firefighting

    You see and test the application from the first weeks, not only on launch day. That makes the launch calm.

    What it gives you

    • A test version available throughout the build
    • Every change checked automatically before release
    • Monitoring running before the first user arrives

    We know about an error before a user notices it, and we fix it quickly.

  • CODE YOU OWN

    The code in your repository after every stage

    The application is the foundation of how your company works, so it cannot depend on one vendor.

    What it gives you

    • The full code in your account from day one, not after the last invoice
    • The rights to the code pass to you, with no exceptions in the contract
    • Only widely used technologies, none of our own closed libraries
    • Handover documentation included

    Your team or a new vendor will find their way around the code in a few weeks.

FOR WHOM dvnt - AND FOR WHOM NOT

Who we build web applications for - and who we don't

We say plainly when a custom application makes sense and when something else is a better choice.

  • A company of 30-150 people that needs its own system

    Excel or an off-the-shelf CRM is no longer enough, and the company needs an application that fits the way it works: a CRM, a client portal, a B2B portal or a dashboard.

    Typical industries

    • Professional services: legal, medical, financial
    • Manufacturers and exporters
    • Online shops with an unusual process
    • Service companies with many locations

    You get an application built around your process, ready to grow, with monitoring and care after launch.

  • An off-the-shelf tool covers most of your needs

    A custom application is an investment for years. If a ready-made tool does most of what you need, buy it instead of building.

    When we usually recommend a ready-made tool

    • A CRM for 10-30 people, e.g. Pipedrive or HubSpot
    • Project management, including industry tools
    • Mailing and marketing automation, e.g. Brevo
    • Bookings, e.g. Calendly or Cal.com
    • Customer support tickets

    In a 15-minute consultation we help you decide: build or buy. Some calls end with a recommendation of a ready-made tool.

  • A startup after its MVP that has outgrown it

    You have a proven business model and the first revenue, but an MVP built with a no-code tool or in a hurry starts to crack as users grow.

    What you get

    • A rebuild or clean-up of the application and a plan for further development
    • Support for many clients and payments
    • Monitoring and documentation that help in talks with investors
  • A prototype in a week for less than a Lean MVP

    If you want to test an idea in a week rather than build an application for hundreds of clients, there are faster and cheaper ways.

    What we recommend

    • No-code tools, e.g. Bubble, FlutterFlow or Glide
    • An experienced freelancer with similar projects in their portfolio
    • An accelerator programme with technical support

    Come back to us when the prototype proves the idea and you need an application ready for a larger scale.

  • A company of 100-300 people outsourcing a module of a larger system

    You have your own IT team, but it is overloaded, and you are looking for a partner for a separate module: a partner portal, a booking system or an ERP integration.

    What you get

    • A module designed for your current architecture
    • Documentation your team can take the code over with
    • The code in your repository
    • A contract that fits your company's procurement process
  • A large enterprise with a multi-country project

    When a project needs to run in several regions at once, a team available around the clock with a 99.99% uptime guarantee, SOC2 or ISO 27001 certification or its own AI infrastructure, we are too small a team.

    Better options

    • Larger software companies, Polish or international
    • An in-house IT team

    For such projects we can deliver a specific module, but not the whole platform.

FAQ

Questions we get during the consultation phase

Questions about web applications: serving many clients, scaling, security, compliance and rebuilding old systems.

When should an application be multi-tenant, and when is single-tenant enough?

Three decision criteria:

  1. Will the application support >1 customer/team/brand in the future 3-5 years?
  • Yes (even hypothetically) → multi-tenant ready from day 1
  • Not sure → multi-tenant ready architecture, but single-tenant deploy (dvnt default)
  • Definitely not → single-tenant (rare in practice)
  1. Is the app ever going to be white-label for resellers?
  • Yes → multi-tenant required, custom branding per tenant
  • No → single-tenant ok
  1. Compliance requirement to isolate data between customers?
  • Yes (medicine GDPR Art. 9, finance FSC) → schema-per-tenant or database-per-tenant
  • Standard business → row-level security in PostgreSQL is enough

dvnt default: every web application has multi-tenant ready architecture (tenant_id in schema, RLS), even if deploy is single-tenant. Convert single → multi in 1-2 sprints instead of 6-month refactoring.

What happens when the app grows from 100 to 10,000 users?

dvnt architecture designed for scaling, but bottlenecks appear at specific thresholds:

100-1,000 users: Zero changes in infrastructure, 1 VPS (4-8 GB RAM, 2-4 vCPU) is enough. Cost PLN 100-300/month.

1,000-10,000 users: Optional read-only PostgreSQL replica for reports (offload primary), Redis cache for hot queries, CDN for static assets. Migration 1-2 sprints. Infrastructure cost PLN 500-1,500/month.

10,000-100,000 users: horizontal scaling (load balancer + 2-4 app servers), read replicas PostgreSQL, queue processing (BullMQ + Redis), edge caching (Cloudflare). Architecture does not require rewriting - modular structure from day 1 allows to scale elements separately. Cost PLN 2,000-8,000/month.

100,000+ users: Decision per case - usually requires re-architecting key modules (sharding, microservices where it makes sense, dedicated infrastructure team). dvnt helps with decisions, but realistically an application with 100k+ users is usually run by a different kind of operator than one with 10k.

Database (PostgreSQL) scales to 1M+ users without re-architecting if queries are well indexed and access patterns predictable.

Does the dvnt stack (Next.js + Payload) create vendor lock-in?

Short answer: no, the stack is open-source, the code yours.

Long answer - what specifically protects against lock-in:

Open-source frameworks:

  • Next.js (MIT license) - developed in the open by Vercel - no "abandoned by the maintainer" risk.
  • Payload CMS (MIT license) - platform ownership for CMS, you can host where you want
  • PostgreSQL (PostgreSQL License) - the most widely used relational database in production, PostgreSQL developer you will find everywhere

No proprietary dvnt libraries:

  • Any relationship inpackage.json has a public npm registry
  • Zero"dvnt Framework" or"dvnt Auth Library". which are not available on npm
  • Configuration deployment in git repo, not in the"dvnt Cloud Console".

Code in your repo:

  • GitHub/GitLab Your License
  • Full git history available
  • Change of developer/agency = pull request, no"dvnt cloud code recovery"

A realistic case from our practice: 2 clients switched to in-house team after 18-24 months. Senior developer found his way around the code in 1-2 weeks (Next.js + PostgreSQL = market standard).

The only"lock-in" it'sarchitectural choice - if the application built on Next.js, migration to Vue/Angular requires a frontend rewrite. This is not unique to dvnt - any agency such"lock-in" creates. dvnt vs. competition: we choose frameworks with 5+ years of track record, not hype-driven.

Is dvnt building applications under GDPR Art. 9 (medicine), FSC (finance) or SOC2?

GDPR Article 9 (sensitive data - medical, biometric data): Yes. Baseline dvnt (encrypted at rest, audit log, RBAC, multi-factor auth) covers core requirements. Discovery (Stage 02) includes GDPR gap analysis - what additionally the application needs (e.g. specific retention policies, consent management, DPIA support). Realistically 4-6 GDPR Art 9 projects completed, mostly medical and HR.

Polish Financial Supervision Authority (KNF, financial sector): In part. Baseline of dvnt web application covers security and audit, butspecific KNF compliance (Recommendations D, M, Z) often requires an external compliance consultant. dvnt works in the mode ofcollaboration - we build the application, client + KNF compliance company validate. 1-2 fintech projects completed (not full banking, but adjacent - B2B fintech, lending platform).

SOC2 / ISO 27001: Not default. These audits requireoperational processes of the company (continuous monitoring, incident response procedures, employee training, physical security data center) - not just a web application. dvnt builds the application with technical SOC2-ready controls (audit log, encryption, access control), butcertification is on the client side Or external SOC2 audit of the company.

HIPAA / GDPR US compliance: No. dvnt works in the Polish, EU and Swiss markets. For US healthcare compliance we recommend specialized companies.

Does dvnt migrate existing applications (PHP legacy, old .NET, custom enterprise)?

Yes, butselectively. Legacy migration is often 60-80% of the budget of a new application, and output only makes sense if the existing systemactually blocks business.

The three migration scenarios we do:

1. UI/frontend migration, backend stays: Most common case. Old PHP/Java/.NET monolith stays, we add a new Next.js frontend communicating with existing backend via API. Time: 8-12 weeks. Risk: low. ROI: fast (client sees modern interface in 2-3 months).

2. step migration (strangler pattern): Old system stays in production, new modules in Next.js + Payload replace legacy modules one by one. Time: 12-24 months. Risk: medium. ROI: spread out, less business disruption.

3. full migration (rebuild): Old system archived (read-only), new system replaces 100% functionality. Time: 16-32 weeks. Risk: high (data migration, user training, rollback strategy). ROI: long-term, but requires business case ROI of 3-5 years.

What we do NOT do:

  • Migration of a stack that dvnt does not use in production (Ruby on Rails legacy, custom mainframe)
  • "Small fixes" In existing legacy code (freelancer scope)
  • Rebuild without clear business case (custom for custom = fail)
Can a mobile app be added to the web app later?

Yes - and we often do. dvnt web application designedAPI-first (Next.js API Routes or a dedicated backend). The mobile app can use the same backend without rewriting the business logic.

Stack mobile: React Native (Expo) - code reuse 60-80% from React/Next.js web application. Shared:

  • Business logic (TypeScript)
  • API client
  • Validation schemas (Zod)
  • Type definitions

What's specific for mobile:

  • UI components (mobile patterns, gesture handling)
  • Push notifications (FCMs/APNs).
  • Offline mode (if required)
  • App Store / Play Store deployment

Typical schedule for adding mobile:

  • 6-10 weeks for companion app (reads/edits same data as web app)
  • 12-16 weeks for feature-rich mobile (offline, push, hardware integration)
  • Price: from PLN 40,000 (companion) to PLN 150,000+ (full custom)

Native (Swift/Kotlin): Only when specific requirements (advanced graphics, performance- critical features, hardware integration like BLE/NFC). In practice dvnt does React Native in 80%+ of mobile projects. For native contractors, we recommend specialized mobile shops.

Does the application need to be on dvnt servers or can I host at my place?

You can host anywhere you want. dvnt does not require deployment on your own infrastructure.

Three deployment models:

1. dvnt-managed VPS (most common, 70% of projects): dvnt puts VPS on your account, configures, monitoring, backups. You pay for the VPS directly (PLN 80-200/month), dvnt pays for maintenance separately (PLN 450-1,500/month). Root access is yours.

2. client-managed (your infrastructure): Your IT team manages the infrastructure - your own VPS, on-premises server, clustered Kubernetes. dvnt conveys:

  • Docker application images
  • Deployment runbook (step-by-step how to deploy)
  • Database migration scripts
  • Configuration template (env vars, secrets)
  • 1-2 knowledge transfer sessions for your team

Mostly for enterprise customers or companies with dedicated DevOps team.

3. Cloud (AWS / GCP / Azure): If the customer already has a cloud ecosystem. dvnt deploys the app to your cloud account, configure IaC (Terraform/ Pulumi) in git repo, you control billing and access.

Key:

  • Code in your git repo - regardless of deployment model
  • Database backups in your cloud storage - zero retention on dvnt infrastructure
  • Secrets (API keys, passwords) in your secrets manager - dvnt does not store customer credentials long-term
  • Migration path - transition from dvnt-managed → client-managed always possible (export Docker images + database dump + configuration)

RESOURCES · BEFORE WE TALK

Before we talk

// Next step

Describe your project. We reply within 24 h.

A few sentences are enough: what should work, what it connects to and by when. No brief, no commitment.

What happens next

  1. We read your message and reply within one working day.
  2. We set up a short call about the scope, with no sales pitch.
  3. You get proposed stages and a price range.
Meeting date (optional)

Time

CET

Checking free times…

Budget (net)

By sending this form, you accept the Privacy Policy.