OUR OFFER - SOFTWARE DEVELOPMENT

Software for companies that have outgrown off-the-shelf tools

Custom CRM, customer dashboard, internal dashboard, B2B portal, mobile app, workflow automation system - when off-the-shelf tools (Excel, basic CRM, Zapier) stop scaling with your business. We build dedicated software that expands over years, no refactoring after a year.

We are not a software house for "agile teams" and "cutting-edge technologies." We are a technology partner for companies that need a dedicated system - and know it's a multi-year investment, not a one-time project.

Most of our software clients are companies of 30-150 people in the scaling phase - Excel is no longer enough, off-the-shelf CRM doesn't address custom workflow, integrations between systems start eating up hours per week. We build a web application, customer panel or automation system - and maintain it for 3-5 years of expansion.

See areas of specialization
Arrange an architectural interview

20+ years of IT - 50+ deployments - Applications - Mobile - Automations.

OUR OFFER - SOFTWARE DEVELOPMENT

Software for companies that have outgrown off-the-shelf tools

Custom CRM, customer dashboard, internal dashboard, B2B portal, mobile app, workflow automation system - when off-the-shelf tools (Excel, basic CRM, Zapier) stop scaling with your business. We build dedicated software that expands over years, no refactoring after a year.

See areas of specialization
Arrange an architectural interview

20+ years of IT - 50+ deployments - Applications - Mobile - Automations.

WHEN IT'S WORTH IT - 4 SIGNALS FROM SCALING

When off-the-shelf tools stop scaling

Four signals at which investment in dedicated software pays off faster than trying to compensate limits of off-the-shelf tools. If you recognize at least two of the four - it's time to talk.

01READY-MADE TOOLS

Excel has become an operational core, but it is no longer enough

The company's operations depend on several dozen Excel sheets: customer base, projects in progress, delivery schedule, bid calculations. Everyone has their own version of the file, data integrity depends on team discipline, mistakes cost real money (bad bids, lost orders, duplicate invoices).

Specific symptoms:

3+ people work on the same sheet and collisions are daily
Excel breaks at 5,000+ records (opening 30+ seconds)
Trail audit is missing (who changed what and when)
Repetitive manual work (copy from sheet to CRM, to invoice, to report)

Dedicated application: single source of truth, roles and permissions, change history, automation of repetitive operations.

02READY CRM/SAAS

Implemented tools force process change instead of support

Off-the-shelf CRM, project management, or industry SaaS - bought, implemented, 50% of the team complains. The company's workflow doesn't match the tool's assumptions, so either the team bypasses the system (Excel comes back through the back door), or the process has been twisted to fit the off-the-shelf solution.

Specific symptoms:

Custom workflow requires 5+ workarounds in the finished tool
30%+ of functions not used because they don't fit the industry/process
Integrations with other systems in the company cost 30-50% per month on top of subscriptions (subscriptions to automation tools, custom scripts)
The customer says "we have CRM, but [accounting/production/suppliers] separately".

Dedicated application: workflow 100% under the company's process, one database, one login, one logic.

03DATA SILOS

Data between systems flows through people, not APIs

Order from Allegro/Baselinker copied manually to accounting. Lead from web form transcribed into CRM. Invoice from accounting re-entered into management report. Each operation is 5-15 minutes + risk of error.

Specific symptoms:

3+ systems in the company, data flows through Excel/email/PDF
Backoffice worker spends >20% of time manually copying data
Management reports are late because data needs to be "downloaded"
Each new customer/supplier = setup in 4-5 systems separately

Dedicated application or automation: API integration, real-time synchronization, single source of truth, automated management reports.

04COMPETITIVE GAP

Competitors offer customers a panel/portal, we handle by email

The B2B customer expects self-service 24/7: order status, invoice history, downloadable documents, claim forms. The competition already has this in the customer panel. You guys handle it by email or phone - speed goes down, costs go up, the customer sees you as a"less professional".

Specific symptoms:

The customer asks "do you have a panel?"
30%+ of the service team's time is repetitive questions about the status of orders/invoices
Returns/complaints generate 5+ emails back and forth
Competitors in the industry have a customer portal, you do not

Dedicated application: customer panel with self-service, reduce repetitive service by 50-70%, signal market professionalism.

↳ If you don't recognize any of the 4 signals - off-the-shelf tools (Excel, HubSpot, Pipedrive, Asana) will probably suffice and are cheaper than dedicated software. We say it plainly instead of pushing an unnecessary investment.

4 AREAS OF SPECIALIZATION - CHOOSE THE TYPE OF PROJECT

What specifically are we building

Each area is a separate sub-page with details: when worthwhile, typical scenarios, stack, process, price fork. Not all areas are expanded at the same time - flagship is the applications web applications (largest demand), the others are expanded in stages.

01WEB APPLICATIONS

Web applications for companies that have outgrown their sheets

Custom CRM - Customer dashboard - B2B portal - Internal dashboard - SaaS.

The largest DV category and the only one with a dedicated pricing calculator. Web applications for specific company workflows - custom CRM when ready-made ones don't fit, customer panels with self-service, B2B portals for partners, internal dashboards aggregating data from multiple systems, SaaS multi-tenant from MVP to product.

Stack: Next.js + Payload CMS + PostgreSQL + API integrations. Modular architecture under expansion for 3-5 years.

Typical project: 6-16 weeks. Price: from PLN 30,000 (calculator available).

→ View web application offerings

02MOBILE APPLICATIONS

Mobile application as an extension of the system

React Native - iOS - Android - Companion apps - Field work

Mobile apps most often as companion to web app - field workforce, mobile-first client, push notifications as business case. Stack React Native allows to share 60-80% of code with web app, one team maintains both systems. Native (Swift/Kotlin) only when specific requirements (advanced graphics, hardware integration).

Typical project: 8-16 weeks. Price: from PLN 40,000.

→ View mobile app offerings

03MVP FOR STARTUPS

An MVP that scales to product - not to refactor

B2B SaaS - Marketplace - Internal tool - Post-seed/pre-Series A

For CTO/CEO of post-seed pre-Series A startups: MVP ready to test business hypothesis, but built as foundation for scale - not throwaway code. Stack production-ready from day one, refactor after growth is adding features, not rewriting the system.

Typical project: 6-8 weeks. Price: MVP from PLN 30,000 (further phases per discussion).

04AUTOMATIZATIONS

Automate the processes that are stealing hours from you every week

Workflow - API integrations - Data sync - Scheduled reports.

Single workflow or automation system for companies that have too many manual operations: email→CRM data entry, batch processing of sheets, sync between systems, scheduled reports. First step: audit existing workflows + prioritize ROI - it often turns out that you only need to automate 3 processes to free up 1 backoffice FTE.

Typical project: 2-8 weeks. Price: single workflow from PLN 15,000, system from PLN 50,000.

→ See automation offerings

↳ Backend and API as part of each of the 4 specialties - stack details in the "Stack and technologies" section (Block 4). We do not do backend as a separate product - backend always under a specific application, integration or system.

WHAT YOU GET - 4 SPECIFICS

What you get when you choose DV as your technology partner

Four things that come with the price of any DV project - no matter whether it's a web app, mobile, MVP or automation. Not upsells, not premium packages - standard.

ARCHITECTURE

System designed for 3-5 year expansion, not launch

Most software projects start as MVP/v1, but realistically live 3-5 years. Architecture designed for this perspective - modular structure, separation of concerns, API versioning, data migrations planned from the beginning.

Concrete decisions:

Monorepo structure (apps/web, apps/admin, packages/ui, packages/database) - add admin panel or mobile app without rewriting
TypeScript strict mode + Zod validation - contracts between modules checked compile-time
Database migrations in versioned code (not"we will do ALTER TABLE in production".)
Feature flags + A/B testing infrastructure from day one

The implication: expansion in 2 years is to add features, not refactor the entire system.

OBSERVABILITY

Handling incidents before the customer notices

Production deployment is not"deploy and pray". Each DV application has a monitoring stack implemented as standard:

Sentry - error tracking with full stack trace, breadcrumbs, user session recordings
Uptime monitoring every 5 minutes, SMS/email alerts for incidents
PostHog - product analytics + session replays (we can see what the user was doing before the error)
Application performance monitoring (response time, DB queries, bottlenecks)
Centralized logging with retention 30 days

Consequence: production error is reported by Us to You, not vice versa. Fix deployed usually in 2-4h after incident. Zero"the application doesn't work, but we don't know what"..

DOCUMENTATION

Code that can be expanded without us

Vendor lock-in is a typical custom software problem - agency builds, client becomes dependent, cost of changing developer is 50-100% of cost of re-implementation. DV works differently.

What you get in a handoff:

Full source code in your GitHub/GitLab repository - your license, your intellectual property
README + CONTRIBUTING.md with instructions for setup local development in 30 minutes
ADR (Architectural Decision Records) - why we chose this stack, these patterns, these trade-offs
Deployment runbook - how to deploy, how to rollback, how to debug production
Database schema documentation + migrations history

Consequence: a client with an active in-house developer will find his way around the code in 1-2 weeks. A client changing developer/agency after 2 years does not lose months of"decryption".

QUALITY CODE.

TypeScript strict, automated tests, code review before merge

"Working code". it's not"good code". It works until the first change - which breaks 3 other places, because no one has tested what depends on what.

DV process standard:

TypeScript strict mode (noImplicitAny, strictNullChecks, noUnusedLocals) - compile-time errors, not runtime production
Playwright E2E testing for critical paths (login, payment, form submit, API contract)
Vitest unit tests for business logic (calculations, validations, transformations)
ESLint + Prettier in CI/CD - merge blocked if it doesn't go through
Code review before each merge to main - 4-eyes principle

Consequence: changing functionality in six months does not break code from a year ago. TypeScript will catch boundary violations. Testing will catch regression. The last line of defense - code review - will catch designe issues.

↳ These 4 elements are in the standard price of a DV project, not upsell. Software houses who offer them as a "premium package" - is a red flag. Not having them as standard means they are not a priority for the team.

STACK - 4 TECHNOLOGY AREAS

Technology stack and architectural decisions

Stack opinionated - each technology in it is for a specific reason, not *"because fashionable "*. Here are four areas: frontend, backend, infrastructure, integrations. We select the stack under project - we do not force one framework on all clients.

01FRONTEND AND UI

Frontend - framework selected for ecosystem and team preferences

The frontend, like the backend, selected during the architectural consultation phase. The decision depends on the client's existing ecosystem, the competence of the team that will maintain the code, and the project requirements (SEO, performance, content density, real-time features).

Web applications - mostly:

Next.js (App Router, React Server Components) - when SEO and performance are critical, the client has no preference
Astro - when the project is a content-heavy site with minimal interactivity (blog, documentation, portal)
Vue / Nuxt - when the client already has a Vue ecosystem in-house (team, libraries, design system)
Angular - for enterprise customers with existing Angular base and required enterprise standards

Mobile applications:

React Native (Expo or bare workflow) - default for mobile as companion app to web app in React/Next.js
Native (Swift/Kotlin) - when specific hardware requirements, advanced graphics, performance-critical features
Flutter - when the client explicitely requires it (not the default in our stack)

UI/UX layer:

Design tokens as CSS variables (framework-agnostic)
Component library in shadcn/ui pattern for React projects
Tailwind CSS + Radix UI for composable accessibility.
Storybook for projects with a larger library of components

What it decides:

Customer team - who maintains the code long-term
Existing ecosystem - design system, libraries, shared components
SEO + content strategy - content-heavy = Astro/Next.js, app-heavy = pure React/Vue
Real-time features - WebSockets, SSE, optimistic UI influence the choice of framework

02Backend and API

Backend - technology selected for business requirements

The backend does not have a "default stack" in DV. The decision is made during the architectural consultation phase, based on the specific requirements of the project:

Node.js + TypeScript - when Next.js / React web application requires tight frontend/backend integration, real-time features (SSE, WebSockets), high-throughput APIs, or fast MVP iteration. Database: PostgreSQL + Prisma ORM (default) or Drizzle (for edge-deployment).

Java / Spring - when the client already has an in-house Java ecosystem (mainframe integrations, existing industry libraries), a requirement for specific enterprise compliance (banking, finance), or when the client's team plans to take over the code and work in JVM.

Python - when core project is data processing, ML/AI integration, or client has existing Python libraries to reuse.

What it decides:

Customer team (who will maintain the long-term code?)
Existing ecosystem (should the new backend integrate with legacy?)
Performance characteristics (high-throughput vs low-latency)
Compliance / regulatory requirements
Libraries available for the problem domain

API architecture and background jobs - REST/GraphQL/gRPC, queue processing, scheduled tasks - are elements selected similarly. There is no"BullMQ in every project". - In one project BullMQ + Redis, in another scheduled tasks in Next.js API Routes, in the third native cron jobs OS-level.

03INFRASTRUCTURE AND DEPLOYMENT

Infrastructure - selection for customer requirements and scale

We select infrastructure for the project, not for the convenience of the agency. Most common scenarios:

VPS (OVH, Hetzner) - 80-90% of Polish customer projects. Coolify or Dokploy as management panel, Docker containers, Traefik load balancer. Cost 80-200 PLN/month, full control over environment.

Cloud (AWS, GCP, Azure) - when the customer already has a cloud ecosystem (e.g., uses Azure AD, AWS S3, GCP BigQuery). Serverless architecture (Lambda, Cloud Functions) for event-driven workflows.

Vercel - for projects requiring global edge network (>200k users/month, customers on 3+ continents), zero DevOps overhead, automated preview deployments per PR.

On-premises - for clients with compliance requirements (medical, financial, public sector). Self-hosted PostgreSQL, custom VPN, audit-compliant configuration.

CI/CD: GitHub Actions or GitLab CI, automated tests + builds

deploy to staging after each merge, production release manual after approval.

04INTEGRATIONS AND AUTOMATION

Integrations - API-first architecture

DV applications are designed to be"understanding the company's ecosystem". - Integrations with other systems in the architecture, not bolt-on after implementation.

Typical integrations in DV projects:

CRM: HubSpot, Pipedrive, Salesforce (REST API + webhooks)
Payments: Stripe, Przelewy24, PayU, BLIK (Polish market)
Marketing automation: Brevo, Mailchimp, ActiveCampaign
Analytics: GA4, Mixpanel, PostHog (event tracking)
Calendaring: Calendly, Cal.com, Google Calendar API
File storage: AWS S3, Cloudflare R2, MinIO (self-hosted)
LLM APIs: OpenAI, Anthropic (for AI-assisted features).
Allegro/Baselinker, ERP/industry accounting (for e-commerce)

Workflow automation: n8n (self-hosted, recommended for control), Make.com (when client is already using), custom Node.js services for complex business logic.

Background processing: scheduled tasks (cron or BullMQ repeating jobs), event-driven architecture (webhooks → queue → worker), real-time sync (Server-Sent Events or WebSockets when required).

↳ Stack opinionated, but not orthodox. If the client has a specific requirement (e.g., "we build in Vue, not React" or "we don't use AWS"), we adapt. Flexibility limit: we don't go into a stack that we don't use ourselves in production (zero competence = zero responsibility).

PROCESS - 5 STAGES - 8-16+ WEEKS5 steps

From architectural consultation to production - in stages

Each DV software project goes through 5 stages. The time duration depends on the scale (8 weeks for a simple application, 16+ for a complex system with many integrations), but the structure is constant. Technology decisions are made at the first two stages - not after the fact *"oh, we're still missing auth "*.

1-2 weeks - free of charge
Architectural consultation
First call (60-90 min) + 1-2 follow-up sessions. We map the business case: what processes the application is supposed to support, what systems exist in the company, what the future functionality roadmap looks like (3-5 years). Based on this, we pre-select the stack - frontend, backend, database, deployment.

Output:
Architectural Decision Record (ADR) v0 - a 1-2 page document with a stack recommendation and 2-3 alternatives. Each decision has a business case (not just a technical one).
2-3 weeks
Discovery and specification
Discovery deep-dive: user research (3-5 interviews with future system users), analysis of existing workflows, data model mapping (how the application will organize data), API integration specification (which external systems, which endpoints, sync frequency, error handling).

Output: 4 documents:
ERD (Entity Relationship Diagram) - database schema.
API contract (OpenAPI 3.0 spec or GraphQL schema).
Integration maps - which external systems, which operations
User stories + acceptance criteria - testable requirements
2-4 weeks
UX/UI + Prototype
Wireframes in low fidelity for all key screens, then design tokens (CSS variables, typography, spacing) and high-fidelity mockups in Figma. Component library in shadcn/ui pattern. Clickable prototype in Figma for approval before coding.
For projects with a client's existing design system (e.g., after DV branding or another supplier) - we adapt to existing guidelines instead of creating from scratch.
Clickable Figma prototype + design tokens as CSS variables ready for import in Tailwind config. Zero hand-translation design → code.
4-10 weeks - 2-week iterations
MVP Development + iteration
Longest stage. We work in 2-week sprints with a review after each sprint. After each merge to main - automated deploy to staging environment. Customer has access to staging from the first sprint - tests features live, gives feedback before launch.
MVP scope: core user journey + critical integrations. Secondary features (reports, advanced settings, edge case handling) - after MVP launch based on real user feedback.
Continuous deployment to staging. Customer tests N+1 feature while working on N+2 - feedback loop 1 week instead of 3-month big-bang launch.
Code quality in CI/CD (TypeScript strict, ESLint, automated tests) - merge blocked if doesn't pass standards.
05
Launch + stabilization + maintenance
Production deployment + monitoring stack (Sentry, Uptime, PostHog, APM) configured before launch. Handoff session 30-45 min: architecture, deployment process, how to debug production, how to push changes. Included: 30 days of stabilization (minor fixes, optimizations, bug fixes discovered in production).

After stabilization 3 options:
End of cooperation - zero lock-in, code yours
Technical care subscription - rate depending on complexity
Expansion of more features - hourly rate for customers with active subscriptions

Handoff documentation:
README + setup instructions (local dev in 30 min)
Architecture Decision Records (why this stack, these patterns)
Deployment runbook (how to deploy, how to rollback, how to debug production)
Database schema docs + migrations history
Integration runbooks (how to set up Stripe webhooks, how to rotate API keys, etc.)

8-16+ wks

TOTAL

8-10 wks

SMALL APPLICATION

16-24+ wks

COMPOSED SYSTEM

↳ Specific schedule after Discovery (Stage 02). Enterprise projects (multi-tenant SaaS, medical/financial compliance, custom auth with hardware key) - 24+ weeks. We consult individually.

HOW WE COUNT THE BUDGET - 4 AREAS

How much does dedicated software cost

Each project priced individually after Discovery - calculator exists for web applications, for other areas a 20-minute conversation is sufficient for a ±15% fork. Below are the starting price spreads and the range of scale in which we work.

01WEB APPLICATIONS

From £29,000

Type	Price	Time
Small	PLN 29-60 thousand.	6-8 weeks
Average	60-120 thousand zlotys	8-12 weeks
Submitted	120-300+ thousand zlotys.	12-20+ weeks

→ Count the cost of the application

02MOBILE APPLICATIONS

From PLN 40,000

Type	Price	Time
Companion app	40-80 thousand zlotys	8-12 weeks
Standalone	80-150 thousand zlotys	12-16 weeks
Full custom	150-250+ thousand zlotys.	16-24+ weeks

03MVP FOR STARTUPS

From PLN 30,000

Type	Price	Time
Lean MVP	PLN 30-50 thousand	6-8 weeks
MVP standard	50-100 thousand zlotys	8-12 weeks
Post-MVP scale	per discussion	ongoing

4 variables that most strongly influence the price

Regardless of the type of project, 4 variables most strongly determine the final price:

Scale (number of users, roles, integrations) - 30-50% price difference within category
Custom workflow vs standard pattern - customer industry-specific workflow requires 20-40% more discovery + development
Integrations - each additional API integration with a third-party system is 5-15k depending on complexity (auth, error handling, rate limits)
Compliance - requirements of RODO Art. 9 (medicine), FSC (finance), enterprise audit - 15-30% more in discovery + documentation

The final price after Stage 02 (Discovery) - then all 4 variables are quantified.

What is NOT included in the project price

Honest scope - which is not included:

Hosting and infrastructure in production (VPS £80-200/month, cloud per usage)
Monitoring tools - Sentry, PostHog, Uptime monitoring (Free for small scale, further from ~$25/month per tool)
External services paid per use (Stripe 1.4-2.9% per transaction, Twilio per SMS, OpenAI per token, etc.).
Domains + SSL (~£100/year)
Apple Developer Account (US$99/year) and Google Play (US$25 one-time) for mobile apps
Campaign marketing (App Store Optimization, ads - this is not our scope, we recommend specialists)
Content (copywriting, product graphics, images) - we can identify proven providers

Long-term costs: usually 5-15% per year of the project value for hosting + technical care + minor extensions.

What our forks don't cover

Heritage scope - what's outside our area of work:

Single Zapier/Make integrations for 1-2 thousand zlotys - this is the scope of a freelancer, not an agency. We recommend specific people we work with.
Lean MVP for 10-15k - with this budget usually a throwaway code is created, which cannot be expanded. It is better to start with a 30k MVP designed for scale, or with no-code (Bubble, Webflow + Zapier) as the first validation of the hypothesis.
Standalone landing pages without business logic - it's a scope/our-offer/website/landing-page, not a web application.
Custom enterprise with budgets of 500+K and requirements of multi-region failover, custom hardware, dedicated support team - fit larger consulting firms (100+ people).

If your project falls into one of the 4 categories above - we say so directly instead of taking a project that we will not do optimally.

Count the cost of a web application Let's talk about your project

↳ Forks based on 50+ DV deployments in last 3 years. Final price ±15% after Discovery (Stage 02). We consult on enterprise projects (multi-tenant SaaS, industry compliance, custom auth with hardware key) on a case-by-case basis - often beyond the upper forks above.

WHAT MAKES US DIFFERENT - 3 THINGS

3 things we do differently than a typical software house

Most software houses look alike: agile teams, modern technologies, fast iteration, agile teams. Three things below are specifics that you won't find in typical presentations you won't find - because they are uncomfortable for agencies and require honest scope in conversation.

01BUILD/BUY HONESTY

We say "don't build" when there is a ready-made solution

Most software houses treat every inquiry as a potential project for the taking. DV works differently: we devote the first 20 minutes of the conversation to verifying whether the client even needs a custom solution.

Specific situations when we say "don't build."

Customer wants CRM for 10 people - Pipedrive for £80/user (~£800/month) better than a custom CRM for £60k that costs 5-10k a year to maintain
Customer wants a booking platform for 1 salon - Calendly
Stripe (£250/month) is enough, custom platform for 80k is overkill for 1 site
Customer wants mailing automation - Brevo/Mailchimp/HubSpot for £200-1500/month better than custom dashboard for 30-50k
Customer wants analytics dashboard - Metabase/Looker Studio (free) + data from existing database better than custom BI for 100k

The consequence: DV loses 15-20% of potential projects every year through this honest scope. The client, on the other hand, saves £50-100k and buys from us when custom actually makes sense.

02DISCOVERY DELIVERABLE

Discovery is deliverable, not "pre-project stage"

Typical software house: Discovery is"free pre-project stage", whose output (usually a presentation) has one purpose - to sell the project. Usually of questionable quality, no real value beyond the project.

DV considers Discovery (Stage 02 of the process) as.deliverable, which the customer pays for separately (typically PLN 5-15k depending on scale). Output:

ERD (Entity Relationship Diagram) - database schema, can be taken to any developer
API contract (OpenAPI 3.0 spec) - a contract that any team can implement
Integration map - which external systems, which operations, sync frequency
User stories + acceptance criteria - testable functional requirements

What it means in practice:

The client after Discovery has 3 options: we continue the project with DV, the client takes the documents to another developer (lower rates, in-house team, freelancer), the client puts the project on hold and comes back in 6 months with a better business decision.

All 3 options are legitimate - that's why Discovery is paid. The customer does not get"free offer", gets real architectural work.

03STABLE STACK

Stack designed for 3-5 years, not for "latest framework"

Frontend and backend frameworks are changing faster than client companies. Every hype library in an agency's portfolio is a potential tech debt for the client in 18 months when maintainers abandon the project or a new version breaks backward compatibility.

DV uses technologies that:

Have a 5+ year production track record
Active maintenance + community 10k+ developers
Stable API (not"may turn into a major release".)
Clear path upgrade (semver, deprecation cycles, migration guides)

What we do NOT use in client projects:

Frameworks/libraries in version 0.x (pre-stable)
Tech preview features from big tech (Server Actions in Next.js 14 waited 6 months to stabilize before going into default stack DV)
Hype-driven"news at the conference" without production-ready credentials
Bleeding edge ML/AI frameworks (LangChain, vector databases) before they stabilize API contracts

Consequence: 2024 DV application codetoday it works and is updatable. Code from a hype framework from 2024 may need a rewrite in 2026 when the project is archived or undergoes a disruptive major update.

For the customer: 3-5 year stability horizon, no"in a year's time we'll see what's current".

FOR WHOM DV - AND FOR WHOM NOT

Who we work best with on software

DV works well with 3 types of software clients. For the 3 types of projects we recommend elsewhere - either to a larger software house, or to a freelancer, or to an off-the-shelf SaaS. Honest scope filter before we talk.

Company of 30-150 people, scaling, custom system as must-have

Your sweet spot at DV. Excel/ready CRM is no longer enough, company traffic requires a dedicated application (custom CRM, customer panel, B2B portal, internal dashboard). Budget 50-150K for first project, decision cycle 2-6 months.

Typical industries: professional services (legal, medical, financial), B2B SaaS for niche markets, e-commerce with custom workflow, manufacturers with exports.

What we give you: dedicated system for your workflow, modular architecture for 3-5 years of expansion, long-term technical care (450-800 PLN/month depending on scale).

Lean MVP for £1-20k / proof-of-concept in a week.

If your budget is PLN 1-20 thousand and you need"applications next week" To show investors - DV is not the best choice. Our minimum project value is 30K (with MVP), because below this budget we will not build an application that makes long-term business sense.

Recommended alternatives:

No-code platforms (Bubble, Webflow, FlutterFlow) - often sufficient for first hypothesis validation
Freelancer senior with a portfolio of similar projects
Startup gas pedal with built-in tech support

Come back to us when the MVP validates the hypothesis and you need a production-ready system under scale.

Company of 100-300 people, outsourcing module of larger system

You have an internal tech team, but overloaded - looking for a partner for a dedicated module (partner portal, booking system, B2B marketplace, custom integration layer). Budget 100-300k, decision cycle 3-9 months with procurement process (RFP, NDA, DPA).

What you get with DV: an external module designed for your existing architecture, handover-ready technical documentation for your in-house team, code in your repo, a contract with enterprise compliance clauses.

Enterprise 1000+ employees, budget 1000+ thousand zloty, multi-region

For enterprise projects with requirements: multi-region failover, custom hardware integration, dedicated support team 24/7, compliance audit (SOC2, ISO 27001), advanced ML/AI infrastructure - DV is too small a team.

Larger consulting firms (100+ people software house, large software house) or international players fit.

Our sweet spot: projects up to 500K budget, teams up to 500 people, scope 1-2 core systems. Above this scale you work with usonly as a supplier of a specific module - not the main contractor for the entire system.

Startup post-seed pre-Series A with scaling plan

You have a validated business case, first revenues, plan Series A in 6-12 months. MVP ready for market testing (validation of business hypothesis), butalready built As a foundation under scale - not throwaway code to rewrite in a year.

Budget 30-100k for MVP + iterative expansion plan. Decision cycle 1-3 months (faster vs. larger companies, but not"build in a week").

What you get at DV: production-ready stack from day one, scaling-ready code (not throwaway), founder-mindset partnership (we understand startup constraints).

Single integrations for $1-3k, work-for-hire scope

A single Zapier/Make integration for 1-3k, minor tweaks to existing code, hotfixes without much scope - this is not our working model. DV worksdesign and (Discovery → Deployment → Long-term care), not hourly for small things.

Recommended alternatives:

Freelancer senior - Useme, Bulldogjob, Pracuj.pl IT
Plattform automation + community templates (n8n.io templates are often sufficient)
Internal team of the client if it has (we know the stack enough to help with the technical decision)

Come back to us when a project grows to 30k+ scope or when a freelancer leaves a tech debt that no one can decipher (realistically 30% of our new projects are"repair after freelancer".).

↳ If you fit one of the 3 profiles on the left - the next step is a 20-minute architectural interview. If you fit into one of the 3 situations on the right - thank you for your time on this page. We recommend ourselves on the recommendation of companies with whom we have worked or with whom we coexist in the market.

FAQ - 5 QUESTIONS ABOUT SOFTWARE

Questions we get before the first software project

Questions about architectural decisions, contract scope, code ownership code, maintenance. Software-specific concerns that are not covered by DV ecosystem FAQs.

01BUILD VS BUY VS NO-CODE
How do I know if I even need custom software?

Three decision tree tests:

Test 1 - is there a ready-made SaaS that covers 70%+ of your needs? If so (Pipedrive for CRM, Calendly for bookings, Brevo for mailing) - buy SaaS, don't build. Custom only makes sense when an off-the-shelf solution forces a process change (or when an off-the-shelf solution doesn't exist for your niche).

Test 2 - does the company have >2 years of stable workflow? If the process changes every 6 months, custom software will"always out of date". Better to wait until stabilization and then build. Shorter horizon = no-code/SaaS.

Test 3 - does custom really affect revenue/cost? Custom CRM saving 1h per week per employee for a company of 50 people = ~£50k per year value. Custom without clear ROI translates into"nice system, but it didn't make money"..

In a 20-minute architectural conversation, DV will walk you through these 3 tests. If a ready-made SaaS is enough - we'll say it outright (15-20% of conversations end with a recommendation"don't build").

02CODE OWNER
Who owns the code and what happens if I change agencies?

The full source code goes into your GitHub/GitLab repository from the first sprint - not after the launch, not after the last invoice. The code isYour intellectual property From the first line.

What this means practically:

Your license, your contract, your git history
You can give access to another developer/agency at any time
You can take the project over to the in-house team - handover docs will help you find your way around in 1-2 weeks
Zero clauses"DV intellectual property". under contract
No vendor lock-in technology - we use open-source/standard frameworks, not proprietary DV libraries

A realistic case from our practice: 2 clients moved to an in-house team (scaling the team) after 18-24 months with DV. The code moved without problems, we are still in contact with them (sometimes we consult on technical decisions, but we do not block their development).

03ESTABLISHMENT
What is the maintenance of the application after the launch and who takes care of it?

After the 30-day stabilization (included in the price of the project), you have 3 options:

Option 1 - Self-hosted, in-house team Your team maintains the application. DV provides full documentation (deployment runbook, ADR, architecture docs). Zero DV subscription. You come back to us when you want expansion.

Option 2 - Subscription Maintenance (most common) Hosting + monitoring + minor fixes + framework updates + bugfixes. Price depends on the scale of the application (450-1500 PLN/month typical). Most software DV customers choose this option.

Option 3 - Long-term partnership Active subscription + occasional larger expansions (new modules, integrations, refactoring). Hourly rate of 220 PLN/hour for clients with active subscription. No annual minimum, no long contracts.

Regardless of the option - the code is yours, changing the model is possible at any time (with a 30-day notice for subscriptions).

04ARCHITECTURE
Who makes architectural decisions and how are they documented?

Architectural decisions (stack, database, deployment, integrations) are made in thetwo phases:

Phase 1 - Architectural Consultation (Phase 01) DV presents a recommendation with a business case. Each decision has 2-3 alternatives + trade-offs. Client accepts, challenges or forces the alternative (if it has a specific requirement, e.g."we build in Vue, not React".).

Phase 2 - Discovery + Specification (Phase 02) Decisions formalized in theADR (Architectural Decision Records) - Documents 1-2 pages per decision, with context, decision, consequences. Live document in git repo of application, editable in future.

What you get in a handoff:

Complete set of ADRs (usually 8-15 documents per project)
Database schema + ER diagram
API contract (OpenAPI 3.0)
Sequence diagrams for critical user flows

Consistency: every decision isexplainable For a new developer/architect in 2 years. Not"someone did that, we don't know why"..

05SCHEDULE
How long does a project realistically take from first call to production?

A realistic schedule for a typical DV project (mid-scale web application, ~£80k budget):

Week 1-2: first interview + architectural consultation (Stage 01) + ADR v0

Week 3-4: written offer + negotiation + acceptance + contract signing

Week 5-7: Discovery and specification (Stage 02) - ERD, API contract, integration map, user stories

Week 8-10: UX/UI + prototype Figma (Stage 03).

Week 11-18: MVP development in 2-week sprints (Stage 04) - staging from sprint 1

Week 19-20: launch + stabilization + handoff (Stage 05)

Total: ~5 months from initial interview to production launch.

For smaller projects (£30-50k): 3-4 months. For larger ones (PLN 150-300k): 6-9 months.

For urgent projects: we can launch in a week from the first call, butwe don't shorten Discovery - is a constant value regardless of the customer's haste. Forced Discovery leads to forced scope and tech debt.

NEXT STEP - 3 PATHS

Choose a path that fits where you are

Every software project starts differently - with a specific budget and scope, from an idea that requires architectural consultation, or from reading before making a decision. Three paths below.

I HAVE A SPECIFIC PROJECT

You know what you're building, you need a quote

Web application with specific scope: custom CRM, customer panel, B2B portal, internal dashboard, SaaS multi-tenant. You know more or less what functions, how many users, what integrations.

Recommendation: start with the web application calculator. 2-4 minutes, result immediately, without registration. If the forks agree with expectations - we arrange an architectural consultation and proceed to a written offer.

→ Count the cost of a web application

I NEED A CONSULTATION

Have a business problem, looking for a technology architect

You know that the current tools (Excel, off-the-shelf CRM, Zapier) are no longer scaling, but you don't know if the answer is a custom application, automation, or migration to another SaaS. A typical Persona 2 situation - a company of 30-150 people in the scaling phase.

Recommendation: 60-90 minutesarchitectural consultation (free). We map business case, verify build/buy decision, select stack. Consultation output: ADR v0 (architectural decision record) + preliminary price range + decision whether to build at all.

STILL WONDERING

You want to understand the subject first

You are not ready for a quote or consultation - you want to read about software development, compare approaches, understand the differences between custom software and no-code/SaaS.

DV has 30+ articles on web apps, MVPs, automation, and calculators + quizzes with no registration. Get back to us when you're ready for a specific conversation.

↳ All three paths are free of charge and require no commitment. The architectural consultation doesn't end with a "salesman follow-up" after 24 hours - we only contact when the reader himself wants it. If the conversation shows that the project does not fit DV, we recommend specific companies we work with.

WHEN IT'S WORTH IT - 4 SIGNALS FROM SCALING

When off-the-shelf tools stop scaling

Four signals at which investment in dedicated software pays off faster than trying to compensate limits of off-the-shelf tools. If you recognize at least two of the four - it's time to talk.

01READY-MADE TOOLS

Excel has become an operational core, but it is no longer enough

Specific symptoms:

3+ people work on the same sheet and collisions are daily
Excel breaks at 5,000+ records (opening 30+ seconds)
Trail audit is missing (who changed what and when)
Repetitive manual work (copy from sheet to CRM, to invoice, to report)

Dedicated application: single source of truth, roles and permissions, change history, automation of repetitive operations.

02READY CRM/SAAS

Implemented tools force process change instead of support

Specific symptoms:

Custom workflow requires 5+ workarounds in the finished tool
30%+ of functions not used because they don't fit the industry/process
Integrations with other systems in the company cost 30-50% per month on top of subscriptions (subscriptions to automation tools, custom scripts)
The customer says "we have CRM, but [accounting/production/suppliers] separately".

Dedicated application: workflow 100% under the company's process, one database, one login, one logic.

03DATA SILOS

Data between systems flows through people, not APIs

Specific symptoms:

3+ systems in the company, data flows through Excel/email/PDF
Backoffice worker spends >20% of time manually copying data
Management reports are late because data needs to be "downloaded"
Each new customer/supplier = setup in 4-5 systems separately

Dedicated application or automation: API integration, real-time synchronization, single source of truth, automated management reports.

04COMPETITIVE GAP

Competitors offer customers a panel/portal, we handle by email

Specific symptoms:

The customer asks "do you have a panel?"
30%+ of the service team's time is repetitive questions about the status of orders/invoices
Returns/complaints generate 5+ emails back and forth
Competitors in the industry have a customer portal, you do not

Dedicated application: customer panel with self-service, reduce repetitive service by 50-70%, signal market professionalism.

4 AREAS OF SPECIALIZATION - CHOOSE THE TYPE OF PROJECT

What specifically are we building

01WEB APPLICATIONS

Web applications for companies that have outgrown their sheets

Custom CRM - Customer dashboard - B2B portal - Internal dashboard - SaaS.

Stack: Next.js + Payload CMS + PostgreSQL + API integrations. Modular architecture under expansion for 3-5 years.

Typical project: 6-16 weeks. Price: from PLN 30,000 (calculator available).

→ View web application offerings

02MOBILE APPLICATIONS

Mobile application as an extension of the system

React Native - iOS - Android - Companion apps - Field work

Typical project: 8-16 weeks. Price: from PLN 40,000.

→ View mobile app offerings

03MVP FOR STARTUPS

An MVP that scales to product - not to refactor

B2B SaaS - Marketplace - Internal tool - Post-seed/pre-Series A

Typical project: 6-8 weeks. Price: MVP from PLN 30,000 (further phases per discussion).

04AUTOMATIZATIONS

Automate the processes that are stealing hours from you every week

Workflow - API integrations - Data sync - Scheduled reports.

Typical project: 2-8 weeks. Price: single workflow from PLN 15,000, system from PLN 50,000.

→ See automation offerings

WHAT YOU GET - 4 SPECIFICS

What you get when you choose DV as your technology partner

Four things that come with the price of any DV project - no matter whether it's a web app, mobile, MVP or automation. Not upsells, not premium packages - standard.

ARCHITECTURE

System designed for 3-5 year expansion, not launch

Concrete decisions:

Monorepo structure (apps/web, apps/admin, packages/ui, packages/database) - add admin panel or mobile app without rewriting
TypeScript strict mode + Zod validation - contracts between modules checked compile-time
Database migrations in versioned code (not"we will do ALTER TABLE in production".)
Feature flags + A/B testing infrastructure from day one

The implication: expansion in 2 years is to add features, not refactor the entire system.

OBSERVABILITY

Handling incidents before the customer notices

Production deployment is not"deploy and pray". Each DV application has a monitoring stack implemented as standard:

Sentry - error tracking with full stack trace, breadcrumbs, user session recordings
Uptime monitoring every 5 minutes, SMS/email alerts for incidents
PostHog - product analytics + session replays (we can see what the user was doing before the error)
Application performance monitoring (response time, DB queries, bottlenecks)
Centralized logging with retention 30 days

Consequence: production error is reported by Us to You, not vice versa. Fix deployed usually in 2-4h after incident. Zero"the application doesn't work, but we don't know what"..

DOCUMENTATION

Code that can be expanded without us

Vendor lock-in is a typical custom software problem - agency builds, client becomes dependent, cost of changing developer is 50-100% of cost of re-implementation. DV works differently.

What you get in a handoff:

Full source code in your GitHub/GitLab repository - your license, your intellectual property
README + CONTRIBUTING.md with instructions for setup local development in 30 minutes
ADR (Architectural Decision Records) - why we chose this stack, these patterns, these trade-offs
Deployment runbook - how to deploy, how to rollback, how to debug production
Database schema documentation + migrations history

Consequence: a client with an active in-house developer will find his way around the code in 1-2 weeks. A client changing developer/agency after 2 years does not lose months of"decryption".

QUALITY CODE.

TypeScript strict, automated tests, code review before merge

"Working code". it's not"good code". It works until the first change - which breaks 3 other places, because no one has tested what depends on what.

DV process standard:

TypeScript strict mode (noImplicitAny, strictNullChecks, noUnusedLocals) - compile-time errors, not runtime production
Playwright E2E testing for critical paths (login, payment, form submit, API contract)
Vitest unit tests for business logic (calculations, validations, transformations)
ESLint + Prettier in CI/CD - merge blocked if it doesn't go through
Code review before each merge to main - 4-eyes principle

STACK - 4 TECHNOLOGY AREAS

Technology stack and architectural decisions

01FRONTEND AND UI

Frontend - framework selected for ecosystem and team preferences

Web applications - mostly:

Next.js (App Router, React Server Components) - when SEO and performance are critical, the client has no preference
Astro - when the project is a content-heavy site with minimal interactivity (blog, documentation, portal)
Vue / Nuxt - when the client already has a Vue ecosystem in-house (team, libraries, design system)
Angular - for enterprise customers with existing Angular base and required enterprise standards

Mobile applications:

React Native (Expo or bare workflow) - default for mobile as companion app to web app in React/Next.js
Native (Swift/Kotlin) - when specific hardware requirements, advanced graphics, performance-critical features
Flutter - when the client explicitely requires it (not the default in our stack)

UI/UX layer:

Design tokens as CSS variables (framework-agnostic)
Component library in shadcn/ui pattern for React projects
Tailwind CSS + Radix UI for composable accessibility.
Storybook for projects with a larger library of components

What it decides:

Customer team - who maintains the code long-term
Existing ecosystem - design system, libraries, shared components
SEO + content strategy - content-heavy = Astro/Next.js, app-heavy = pure React/Vue
Real-time features - WebSockets, SSE, optimistic UI influence the choice of framework

02Backend and API

Backend - technology selected for business requirements

The backend does not have a "default stack" in DV. The decision is made during the architectural consultation phase, based on the specific requirements of the project:

Python - when core project is data processing, ML/AI integration, or client has existing Python libraries to reuse.

What it decides:

Customer team (who will maintain the long-term code?)
Existing ecosystem (should the new backend integrate with legacy?)
Performance characteristics (high-throughput vs low-latency)
Compliance / regulatory requirements
Libraries available for the problem domain

03INFRASTRUCTURE AND DEPLOYMENT

Infrastructure - selection for customer requirements and scale

We select infrastructure for the project, not for the convenience of the agency. Most common scenarios:

VPS (OVH, Hetzner) - 80-90% of Polish customer projects. Coolify or Dokploy as management panel, Docker containers, Traefik load balancer. Cost 80-200 PLN/month, full control over environment.

Cloud (AWS, GCP, Azure) - when the customer already has a cloud ecosystem (e.g., uses Azure AD, AWS S3, GCP BigQuery). Serverless architecture (Lambda, Cloud Functions) for event-driven workflows.

Vercel - for projects requiring global edge network (>200k users/month, customers on 3+ continents), zero DevOps overhead, automated preview deployments per PR.

On-premises - for clients with compliance requirements (medical, financial, public sector). Self-hosted PostgreSQL, custom VPN, audit-compliant configuration.

CI/CD: GitHub Actions or GitLab CI, automated tests + builds

deploy to staging after each merge, production release manual after approval.

04INTEGRATIONS AND AUTOMATION

Integrations - API-first architecture

DV applications are designed to be"understanding the company's ecosystem". - Integrations with other systems in the architecture, not bolt-on after implementation.

Typical integrations in DV projects:

CRM: HubSpot, Pipedrive, Salesforce (REST API + webhooks)
Payments: Stripe, Przelewy24, PayU, BLIK (Polish market)
Marketing automation: Brevo, Mailchimp, ActiveCampaign
Analytics: GA4, Mixpanel, PostHog (event tracking)
Calendaring: Calendly, Cal.com, Google Calendar API
File storage: AWS S3, Cloudflare R2, MinIO (self-hosted)
LLM APIs: OpenAI, Anthropic (for AI-assisted features).
Allegro/Baselinker, ERP/industry accounting (for e-commerce)

Workflow automation: n8n (self-hosted, recommended for control), Make.com (when client is already using), custom Node.js services for complex business logic.

Background processing: scheduled tasks (cron or BullMQ repeating jobs), event-driven architecture (webhooks → queue → worker), real-time sync (Server-Sent Events or WebSockets when required).

PROCESS - 5 STAGES - 8-16+ WEEKS5 steps

From architectural consultation to production - in stages

1-2 weeks - free of charge
Architectural consultation
First call (60-90 min) + 1-2 follow-up sessions. We map the business case: what processes the application is supposed to support, what systems exist in the company, what the future functionality roadmap looks like (3-5 years). Based on this, we pre-select the stack - frontend, backend, database, deployment.

Output:
Architectural Decision Record (ADR) v0 - a 1-2 page document with a stack recommendation and 2-3 alternatives. Each decision has a business case (not just a technical one).
2-3 weeks
Discovery and specification
Discovery deep-dive: user research (3-5 interviews with future system users), analysis of existing workflows, data model mapping (how the application will organize data), API integration specification (which external systems, which endpoints, sync frequency, error handling).

Output: 4 documents:
ERD (Entity Relationship Diagram) - database schema.
API contract (OpenAPI 3.0 spec or GraphQL schema).
Integration maps - which external systems, which operations
User stories + acceptance criteria - testable requirements
2-4 weeks
UX/UI + Prototype
Wireframes in low fidelity for all key screens, then design tokens (CSS variables, typography, spacing) and high-fidelity mockups in Figma. Component library in shadcn/ui pattern. Clickable prototype in Figma for approval before coding.
For projects with a client's existing design system (e.g., after DV branding or another supplier) - we adapt to existing guidelines instead of creating from scratch.
Clickable Figma prototype + design tokens as CSS variables ready for import in Tailwind config. Zero hand-translation design → code.
4-10 weeks - 2-week iterations
MVP Development + iteration
Longest stage. We work in 2-week sprints with a review after each sprint. After each merge to main - automated deploy to staging environment. Customer has access to staging from the first sprint - tests features live, gives feedback before launch.
MVP scope: core user journey + critical integrations. Secondary features (reports, advanced settings, edge case handling) - after MVP launch based on real user feedback.
Continuous deployment to staging. Customer tests N+1 feature while working on N+2 - feedback loop 1 week instead of 3-month big-bang launch.
Code quality in CI/CD (TypeScript strict, ESLint, automated tests) - merge blocked if doesn't pass standards.
05
Launch + stabilization + maintenance
Production deployment + monitoring stack (Sentry, Uptime, PostHog, APM) configured before launch. Handoff session 30-45 min: architecture, deployment process, how to debug production, how to push changes. Included: 30 days of stabilization (minor fixes, optimizations, bug fixes discovered in production).

After stabilization 3 options:
End of cooperation - zero lock-in, code yours
Technical care subscription - rate depending on complexity
Expansion of more features - hourly rate for customers with active subscriptions

Handoff documentation:
README + setup instructions (local dev in 30 min)
Architecture Decision Records (why this stack, these patterns)
Deployment runbook (how to deploy, how to rollback, how to debug production)
Database schema docs + migrations history
Integration runbooks (how to set up Stripe webhooks, how to rotate API keys, etc.)

8-16+ wks

TOTAL

8-10 wks

SMALL APPLICATION

16-24+ wks

COMPOSED SYSTEM

↳ Specific schedule after Discovery (Stage 02). Enterprise projects (multi-tenant SaaS, medical/financial compliance, custom auth with hardware key) - 24+ weeks. We consult individually.

HOW WE COUNT THE BUDGET - 4 AREAS

How much does dedicated software cost

01WEB APPLICATIONS

From £29,000

Type	Price	Time
Small	PLN 29-60 thousand.	6-8 weeks
Average	60-120 thousand zlotys	8-12 weeks
Submitted	120-300+ thousand zlotys.	12-20+ weeks

→ Count the cost of the application

02MOBILE APPLICATIONS

From PLN 40,000

Type	Price	Time
Companion app	40-80 thousand zlotys	8-12 weeks
Standalone	80-150 thousand zlotys	12-16 weeks
Full custom	150-250+ thousand zlotys.	16-24+ weeks

03MVP FOR STARTUPS

From PLN 30,000

Type	Price	Time
Lean MVP	PLN 30-50 thousand	6-8 weeks
MVP standard	50-100 thousand zlotys	8-12 weeks
Post-MVP scale	per discussion	ongoing

4 variables that most strongly influence the price

Regardless of the type of project, 4 variables most strongly determine the final price:

Scale (number of users, roles, integrations) - 30-50% price difference within category
Custom workflow vs standard pattern - customer industry-specific workflow requires 20-40% more discovery + development
Integrations - each additional API integration with a third-party system is 5-15k depending on complexity (auth, error handling, rate limits)
Compliance - requirements of RODO Art. 9 (medicine), FSC (finance), enterprise audit - 15-30% more in discovery + documentation

The final price after Stage 02 (Discovery) - then all 4 variables are quantified.

What is NOT included in the project price

Honest scope - which is not included:

Hosting and infrastructure in production (VPS £80-200/month, cloud per usage)
Monitoring tools - Sentry, PostHog, Uptime monitoring (Free for small scale, further from ~$25/month per tool)
External services paid per use (Stripe 1.4-2.9% per transaction, Twilio per SMS, OpenAI per token, etc.).
Domains + SSL (~£100/year)
Apple Developer Account (US$99/year) and Google Play (US$25 one-time) for mobile apps
Campaign marketing (App Store Optimization, ads - this is not our scope, we recommend specialists)
Content (copywriting, product graphics, images) - we can identify proven providers

Long-term costs: usually 5-15% per year of the project value for hosting + technical care + minor extensions.

What our forks don't cover

Heritage scope - what's outside our area of work:

Single Zapier/Make integrations for 1-2 thousand zlotys - this is the scope of a freelancer, not an agency. We recommend specific people we work with.
Lean MVP for 10-15k - with this budget usually a throwaway code is created, which cannot be expanded. It is better to start with a 30k MVP designed for scale, or with no-code (Bubble, Webflow + Zapier) as the first validation of the hypothesis.
Standalone landing pages without business logic - it's a scope/our-offer/website/landing-page, not a web application.
Custom enterprise with budgets of 500+K and requirements of multi-region failover, custom hardware, dedicated support team - fit larger consulting firms (100+ people).

If your project falls into one of the 4 categories above - we say so directly instead of taking a project that we will not do optimally.

Count the cost of a web application Let's talk about your project

WHAT MAKES US DIFFERENT - 3 THINGS

3 things we do differently than a typical software house

01BUILD/BUY HONESTY

We say "don't build" when there is a ready-made solution

Specific situations when we say "don't build."

Customer wants CRM for 10 people - Pipedrive for £80/user (~£800/month) better than a custom CRM for £60k that costs 5-10k a year to maintain
Customer wants a booking platform for 1 salon - Calendly
Stripe (£250/month) is enough, custom platform for 80k is overkill for 1 site
Customer wants mailing automation - Brevo/Mailchimp/HubSpot for £200-1500/month better than custom dashboard for 30-50k
Customer wants analytics dashboard - Metabase/Looker Studio (free) + data from existing database better than custom BI for 100k

The consequence: DV loses 15-20% of potential projects every year through this honest scope. The client, on the other hand, saves £50-100k and buys from us when custom actually makes sense.

02DISCOVERY DELIVERABLE

Discovery is deliverable, not "pre-project stage"

DV considers Discovery (Stage 02 of the process) as.deliverable, which the customer pays for separately (typically PLN 5-15k depending on scale). Output:

ERD (Entity Relationship Diagram) - database schema, can be taken to any developer
API contract (OpenAPI 3.0 spec) - a contract that any team can implement
Integration map - which external systems, which operations, sync frequency
User stories + acceptance criteria - testable functional requirements

What it means in practice:

All 3 options are legitimate - that's why Discovery is paid. The customer does not get"free offer", gets real architectural work.

03STABLE STACK

Stack designed for 3-5 years, not for "latest framework"

DV uses technologies that:

Have a 5+ year production track record
Active maintenance + community 10k+ developers
Stable API (not"may turn into a major release".)
Clear path upgrade (semver, deprecation cycles, migration guides)

What we do NOT use in client projects:

Frameworks/libraries in version 0.x (pre-stable)
Tech preview features from big tech (Server Actions in Next.js 14 waited 6 months to stabilize before going into default stack DV)
Hype-driven"news at the conference" without production-ready credentials
Bleeding edge ML/AI frameworks (LangChain, vector databases) before they stabilize API contracts

For the customer: 3-5 year stability horizon, no"in a year's time we'll see what's current".

FOR WHOM DV - AND FOR WHOM NOT

Who we work best with on software

Company of 30-150 people, scaling, custom system as must-have

Typical industries: professional services (legal, medical, financial), B2B SaaS for niche markets, e-commerce with custom workflow, manufacturers with exports.

What we give you: dedicated system for your workflow, modular architecture for 3-5 years of expansion, long-term technical care (450-800 PLN/month depending on scale).

Lean MVP for £1-20k / proof-of-concept in a week.

Recommended alternatives:

No-code platforms (Bubble, Webflow, FlutterFlow) - often sufficient for first hypothesis validation
Freelancer senior with a portfolio of similar projects
Startup gas pedal with built-in tech support

Come back to us when the MVP validates the hypothesis and you need a production-ready system under scale.

Company of 100-300 people, outsourcing module of larger system

Enterprise 1000+ employees, budget 1000+ thousand zloty, multi-region

Larger consulting firms (100+ people software house, large software house) or international players fit.

Startup post-seed pre-Series A with scaling plan

Budget 30-100k for MVP + iterative expansion plan. Decision cycle 1-3 months (faster vs. larger companies, but not"build in a week").

What you get at DV: production-ready stack from day one, scaling-ready code (not throwaway), founder-mindset partnership (we understand startup constraints).

Single integrations for $1-3k, work-for-hire scope

Recommended alternatives:

Freelancer senior - Useme, Bulldogjob, Pracuj.pl IT
Plattform automation + community templates (n8n.io templates are often sufficient)
Internal team of the client if it has (we know the stack enough to help with the technical decision)

Come back to us when a project grows to 30k+ scope or when a freelancer leaves a tech debt that no one can decipher (realistically 30% of our new projects are"repair after freelancer".).

FAQ - 5 QUESTIONS ABOUT SOFTWARE

Questions we get before the first software project

Questions about architectural decisions, contract scope, code ownership code, maintenance. Software-specific concerns that are not covered by DV ecosystem FAQs.

01BUILD VS BUY VS NO-CODE
How do I know if I even need custom software?

Three decision tree tests:

02CODE OWNER
Who owns the code and what happens if I change agencies?

The full source code goes into your GitHub/GitLab repository from the first sprint - not after the launch, not after the last invoice. The code isYour intellectual property From the first line.

What this means practically:

Your license, your contract, your git history
You can give access to another developer/agency at any time
You can take the project over to the in-house team - handover docs will help you find your way around in 1-2 weeks
Zero clauses"DV intellectual property". under contract
No vendor lock-in technology - we use open-source/standard frameworks, not proprietary DV libraries

03ESTABLISHMENT
What is the maintenance of the application after the launch and who takes care of it?

After the 30-day stabilization (included in the price of the project), you have 3 options:

Regardless of the option - the code is yours, changing the model is possible at any time (with a 30-day notice for subscriptions).

04ARCHITECTURE
Who makes architectural decisions and how are they documented?

Architectural decisions (stack, database, deployment, integrations) are made in thetwo phases:

What you get in a handoff:

Complete set of ADRs (usually 8-15 documents per project)
Database schema + ER diagram
API contract (OpenAPI 3.0)
Sequence diagrams for critical user flows

Consistency: every decision isexplainable For a new developer/architect in 2 years. Not"someone did that, we don't know why"..

05SCHEDULE
How long does a project realistically take from first call to production?

A realistic schedule for a typical DV project (mid-scale web application, ~£80k budget):

Week 1-2: first interview + architectural consultation (Stage 01) + ADR v0

Week 3-4: written offer + negotiation + acceptance + contract signing

Week 5-7: Discovery and specification (Stage 02) - ERD, API contract, integration map, user stories

Week 8-10: UX/UI + prototype Figma (Stage 03).

Week 11-18: MVP development in 2-week sprints (Stage 04) - staging from sprint 1

Week 19-20: launch + stabilization + handoff (Stage 05)

Total: ~5 months from initial interview to production launch.

For smaller projects (£30-50k): 3-4 months. For larger ones (PLN 150-300k): 6-9 months.

NEXT STEP - 3 PATHS

Choose a path that fits where you are

Every software project starts differently - with a specific budget and scope, from an idea that requires architectural consultation, or from reading before making a decision. Three paths below.

I HAVE A SPECIFIC PROJECT

You know what you're building, you need a quote

Web application with specific scope: custom CRM, customer panel, B2B portal, internal dashboard, SaaS multi-tenant. You know more or less what functions, how many users, what integrations.

→ Count the cost of a web application

I NEED A CONSULTATION

Have a business problem, looking for a technology architect

STILL WONDERING

You want to understand the subject first

You are not ready for a quote or consultation - you want to read about software development, compare approaches, understand the differences between custom software and no-code/SaaS.

DV has 30+ articles on web apps, MVPs, automation, and calculators + quizzes with no registration. Get back to us when you're ready for a specific conversation.

Software for companies that have outgrown off-the-shelf tools

Software for companies that have outgrown off-the-shelf tools

When off-the-shelf tools stop scaling

Excel has become an operational core, but it is no longer enough

Implemented tools force process change instead of support

Data between systems flows through people, not APIs

Competitors offer customers a panel/portal, we handle by email

What specifically are we building

Web applications for companies that have outgrown their sheets

Custom CRM - Customer dashboard - B2B portal - Internal dashboard - SaaS.

Mobile application as an extension of the system

React Native - iOS - Android - Companion apps - Field work

An MVP that scales to product - not to refactor

B2B SaaS - Marketplace - Internal tool - Post-seed/pre-Series A

Automate the processes that are stealing hours from you every week

Workflow - API integrations - Data sync - Scheduled reports.

What you get when you choose DV as your technology partner

System designed for 3-5 year expansion, not launch

Handling incidents before the customer notices

Code that can be expanded without us

TypeScript strict, automated tests, code review before merge

Technology stack and architectural decisions

Frontend - framework selected for ecosystem and team preferences

Backend - technology selected for business requirements

Infrastructure - selection for customer requirements and scale

Integrations - API-first architecture

From architectural consultation to production - in stages

How much does dedicated software cost

From £29,000

From PLN 40,000

From PLN 30,000

4 variables that most strongly influence the price

What is NOT included in the project price

What our forks don't cover

3 things we do differently than a typical software house

We say "don't build" when there is a ready-made solution

Discovery is deliverable, not "pre-project stage"

Stack designed for 3-5 years, not for "latest framework"

Who we work best with on software

Company of 30-150 people, scaling, custom system as must-have

Lean MVP for £1-20k / proof-of-concept in a week.

Company of 100-300 people, outsourcing module of larger system

Enterprise 1000+ employees, budget 1000+ thousand zloty, multi-region

Startup post-seed pre-Series A with scaling plan

Single integrations for $1-3k, work-for-hire scope

Questions we get before the first software project

01|BUILD VS BUY VS NO-CODEHow do I know if I even need custom software?

02|CODE OWNERWho owns the code and what happens if I change agencies?

03|ESTABLISHMENTWhat is the maintenance of the application after the launch and who takes care of it?

04|ARCHITECTUREWho makes architectural decisions and how are they documented?

05|SCHEDULEHow long does a project realistically take from first call to production?

Choose a path that fits where you are

You know what you're building, you need a quote

Have a business problem, looking for a technology architect

You want to understand the subject first

When off-the-shelf tools stop scaling

Excel has become an operational core, but it is no longer enough

Implemented tools force process change instead of support

Data between systems flows through people, not APIs

Competitors offer customers a panel/portal, we handle by email

What specifically are we building

Web applications for companies that have outgrown their sheets

Custom CRM - Customer dashboard - B2B portal - Internal dashboard - SaaS.

Mobile application as an extension of the system

React Native - iOS - Android - Companion apps - Field work

An MVP that scales to product - not to refactor

B2B SaaS - Marketplace - Internal tool - Post-seed/pre-Series A

Automate the processes that are stealing hours from you every week

Workflow - API integrations - Data sync - Scheduled reports.

What you get when you choose DV as your technology partner

System designed for 3-5 year expansion, not launch

Handling incidents before the customer notices

Code that can be expanded without us

TypeScript strict, automated tests, code review before merge

Technology stack and architectural decisions

Frontend - framework selected for ecosystem and team preferences

Backend - technology selected for business requirements

Infrastructure - selection for customer requirements and scale

Integrations - API-first architecture

From architectural consultation to production - in stages

01BUILD VS BUY VS NO-CODE
How do I know if I even need custom software?

02CODE OWNER
Who owns the code and what happens if I change agencies?

03ESTABLISHMENT
What is the maintenance of the application after the launch and who takes care of it?

04ARCHITECTURE
Who makes architectural decisions and how are they documented?

05SCHEDULE
How long does a project realistically take from first call to production?

01BUILD VS BUY VS NO-CODE
How do I know if I even need custom software?

02CODE OWNER
Who owns the code and what happens if I change agencies?

03ESTABLISHMENT
What is the maintenance of the application after the launch and who takes care of it?

04ARCHITECTURE
Who makes architectural decisions and how are they documented?

05SCHEDULE
How long does a project realistically take from first call to production?