TECHNOLOGY · PROCESS · SUPPORT
How we build software
For anyone comparing vendors: which technology we use and why, what a project looks like from the first conversation to support after launch, what drives the price and who we work best with.
Technology · a five-stage process · pricing · code ownership
WHEN IT PAYS · FOUR GROWTH SIGNALS
When off-the-shelf tools stop scaling
Four signals at which investing in dedicated software pays off faster than trying to work around the limits of off-the-shelf tools. If you recognise at least two of the four — it's time to talk.
OFF-THE-SHELF TOOLS
Excel has become an operational core, but it is no longer enough
Several people work on the same spreadsheets, there is no change history and data is retyped by hand. An application gives one source of data, permissions and a change history.
OFF-THE-SHELF CRM/SAAS
Off-the-shelf tools force a change of process instead of supporting it
The team works around the off-the-shelf tool because it does not fit how you work, and Excel creeps back in. An application follows your process instead of bending it.
DATA SILOS
Data between systems flows through people, not APIs
People carry data between systems: orders into accounting, enquiries into the CRM. An API integration does it on its own, without mistakes.
COMPETITIVE GAP
Competitors offer customers a panel/portal, we handle by email
Customers expect a portal with order status and invoices, and you answer by email. A customer portal takes over the repetitive questions.
// WHAT YOU GET · FOUR SPECIFICS
What you get when you choose dvnt as your technology partner
Four things that are included in the price of every dvnt project — whether it is a web app, mobile app, MVP or automation. No upsells, no premium packages — it is standard.
ARCHITECTURE
A system designed for 3–5 years of growth, not just for launch
Architecture designed for years of growth, not just the launch: new features are added without rebuilding the system.
OBSERVABILITY
Incidents handled before the customer notices
Error and uptime monitoring from day one — we learn about an outage before you do.
DOCUMENTATION
Code you can extend without us
The code, the repository and the record of decisions are yours. Another team can take the project over without weeks of decoding.
CODE QUALITY
TypeScript strict, automated tests, code review before merge
Strict typing, automated tests and code review — a change in six months does not break what already works.
TECHNOLOGY · FOUR AREAS
Technology stack and architectural decisions
Technologies chosen deliberately — each is here for a specific reason, not *“because it is trendy”*. Below are four areas: frontend, backend, infrastructure, integrations. We choose technology to suit the project — we do not force one framework on every client.
FRONTEND AND UI
Frontend — a framework chosen to fit the ecosystem and the team's preferences
We choose the framework for the project and the team that will maintain the code — most often Next.js, and React Native for mobile apps.
Backend and API
Backend — technology chosen to fit the business requirements
We choose the back end for the requirements: most often Node.js with TypeScript and PostgreSQL, Java or Python when needed.
INFRASTRUCTURE AND DEPLOYMENT
Infrastructure — chosen to fit the client's requirements and scale
A server in Poland or the EU, a cloud or your own servers — depending on scale and requirements. Automated deployments, release after approval.
INTEGRATIONS AND AUTOMATION
Integrations - API-first architecture
Integrations are part of the architecture from the start: CRM, payments, calendars, accounting, e-commerce and AI models.
// PROCESS · FIVE STAGES
From architecture consultation to production, in stages
Every project goes through five stages. The time depends on the project — we set it once the scope is agreed; the smallest builds take from 3 weeks. Technology decisions are made in the first two stages.
free of charge
Architecture consultation
We talk about the goal, the processes and the systems in the company, and choose the technology. Result: a short document with a recommendation.
Analysis (discovery) and specification
Interviews with future users, the data model and an integration map. Result: a specification any team can work from.
UX/UI + Prototype
Sketches, interface design and a clickable prototype to approve before coding.
MVP build + iteration
We build the main path and the key integrations; you test on a staging environment from the start.
Launch + stabilisation + maintenance
Launch with monitoring, handover of the documentation and 30 days of stabilisation. Then: the end of the work, maintenance or further development.
- TOTAL
- 8-16+ wks
- SMALL APPLICATION
- 8-10 wks
- COMPLEX SYSTEM
- 16-24+ wks
↳ The specific schedule is set after the analysis (Stage 02). Enterprise projects (multi-tenant SaaS, medical/financial compliance, custom login with a hardware key) — 24+ weeks. We discuss these individually.
HOW WE CALCULATE THE BUDGET · THREE AREAS
How much does dedicated software cost
Every project is quoted individually after the scope analysis. Below are the starting prices.
WEB APPLICATIONS
From PLN 30,000
MOBILE APPS
From PLN 40,000
MVP FOR STARTUPS
From PLN 10,000
Four variables that influence the price most
Price depends most on scale, how unusual the process is, the number of integrations and regulatory requirements. You know the final price after the analysis.
What is NOT included in the project price
Outside the project price: hosting, paid tools and third-party services, domains, app store accounts, marketing and content.
What our price ranges do not cover
We do not take small automations, throwaway prototypes, simple landing pages or large corporate projects — we say so plainly and recommend someone better suited.
// WHAT SETS US APART · THREE THINGS
Three things we do differently from a typical software house
Most software companies look alike: agile teams, modern technologies, fast iterations, flexible working. The three things below are specifics you will not find in typical presentations — because they are awkward for an agency and require an honest conversation about scope.
BUILD OR BUY
We say “don't build” when a ready-made solution exists
If an off-the-shelf tool is enough, we say so plainly — even if it costs us the project.
ANALYSIS AS A DELIVERABLE
Analysis is a deliverable, not a “stage before the project”
The analysis is a result in its own right: you can take the specification to any vendor.
STABLE TECHNOLOGY
Technologies chosen for 3–5 years, not for the “newest framework”
We use proven, actively developed technology so the code keeps working and can be updated for years.
Fit
Who we work best with
Three client profiles we work with best, and three situations in which we honestly recommend someone else: a larger software house, a freelancer or an off-the-shelf tool.
We work best with
A company of 30–150 people that has outgrown off-the-shelf tools
Excel or an off-the-shelf CRM is no longer enough — it needs its own system.
A company of 100–300 people outsourcing a module of a larger system
You have an IT team, but no spare hands for a self-contained module.
A startup after its seed round, before Series A
The MVP has to test the market and be a foundation for growth.
We recommend someone else when
The budget is below PLN 10,000 or the app is needed “yesterday”
The smallest project we take on is a Lean MVP from PLN 10,000.
It is a corporation of 1,000+ people with a budget above a million
Many regions, 24/7 support, SOC 2 and ISO 27001 audits.
It is a single integration for PLN 1,000–3,000 or minor fixes
We work in projects, not on small one-off jobs.
FAQ · FIVE QUESTIONS ABOUT SOFTWARE
Questions we get before a first software project
Questions about architectural decisions, contract scope, code ownership and maintenance. Software-specific issues that the general dvnt FAQ does not cover.
How do I know if I even need custom software?
Three tests that lead to a decision:
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 — has the company had a stable way of working for over 2 years? If the process changes every 6 months, custom software will be"always out of date". Better to wait until things stabilise and then build. A shorter horizon = no-code/SaaS.
Test 3 — does a custom solution genuinely affect revenue or costs? A custom CRM saving 1 hour a week per employee in a company of 50 people = ~PLN 50,000 a year in value. A custom system without a clear return on investment turns into“nice system, but it didn't make money”.
In a 15-minute architecture call, dvnt will take you through these three tests. If a ready-made SaaS is enough, we will say so directly (15–20% of calls end with a recommendation"don't build").
Who owns the code and what happens if I change agencies?
The full source code goes into your GitHub/GitLab repository after every stage — not only after 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 hand the project over to your own team — the handover documentation lets them get their bearings in 1–2 weeks
- No clauses“dvnt intellectual property” in the contract
- No technological vendor lock-in — we use open, standard frameworks, not proprietary dvnt libraries
Real cases from our practice: 2 clients moved to their own team after 18–24 months with dvnt. The code moved over without problems and we are still in touch (we sometimes consult on technical decisions, but we do not block their development).
What does maintenance of the application look like after launch, and who handles 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. dvnt provides full documentation (deployment runbook, ADR, architecture docs). Zero dvnt subscription. You come back to us when you want expansion.
Option 2 — Ongoing technical support on subscription (most common) Hosting + monitoring + minor fixes + framework updates + bug fixes. The price depends on the scale of the application (typically PLN 450-1,500/month). Most dvnt software clients choose this option.
Option 3 — Long-term partnership Active subscription + occasional larger extensions (new modules, integrations, rebuilds). No annual minimum, no long contracts.
Whichever option you choose, the code is yours and you can change model at any time (with 30 days' notice for subscriptions).
Who makes the architecture decisions and how are they documented?
Architectural decisions (stack, database, deployment, integrations) are made in thetwo phases:
Phase 1 — Architecture consultation (Stage 01) dvnt presents a recommendation with a business rationale. Each decision has 2–3 alternatives + their pros and cons. The client accepts, challenges or picks an alternative (if they have a specific requirement, e.g.“we build in Vue, not React”).
Phase 2 — Analysis + specification (Stage 02) Decisions formalised in theADR (Architectural Decision Records) — documents of 1–2 pages per decision: context, decision, consequences. A living document in the application's repository, editable in future.
What you get on handover:
- Complete set of ADRs (usually 8-15 documents per project)
- Database schema + ER diagram
- API contract (OpenAPI)
- Sequence diagrams for critical user flows
The upshot: every decision isunderstandable to a new developer/architect two years from now. Not“someone did it that way and we don't know why”.
How long does a project realistically take from first call to production?
A realistic schedule for a typical dvnt project (mid-scale web application, ~PLN 80,000 budget):
Week 1–2: first conversation + architecture consultation (Stage 01) + ADR v0
Week 3-4: written offer + negotiation + acceptance + contract signing
Week 5–7: analysis and specification (Stage 02) — ERD, API contract, integration map, user stories
Week 8–10: UX/UI + Figma prototype (Stage 03)
Week 11-18: MVP development in 2-week sprints (Stage 04) - staging from sprint 1
Week 19–20: launch + stabilisation + handover (Stage 05)
Total: ~5 months from initial interview to production launch.
For smaller projects (PLN 30,000-50,000): 3–4 months. For larger ones (PLN 150,000-300,000): 6–9 months.
For urgent projects: we can start within a week of the first call, butwe don't shorten the analysis — that is a constant, however much of a rush the client is in. A forced analysis leads to a forced scope and technical debt.
How does a SaaS application differ from a custom-built system?
A custom system serves one company and is tailored to its processes. A SaaS application is sold to many companies on subscription — each with its own data, users and plan.
The difference lies in the architecture: SaaS needs separated customer data (multi-tenant), recurring payments, plan limits and sign-up without your team's involvement. That is why a SaaS quote starts with the question of how many customers it has to serve in a year, not only which features it needs.
Will you integrate with our ERP?
Yes. We start by checking what the ERP exposes: an API, file exports, database access or the vendor's middleware. That determines whether synchronisation can run in real time or in cycles, e.g. every hour.
We also agree which system is the source of truth for each piece of data — so that the ERP and the new application do not overwrite each other.
Can you take over a system you did not build?
Yes, but always starting with a review: code, infrastructure, documentation, backups, access. After the review you get a prioritised list of risks and a recommendation: we develop it further, fix it in stages or rewrite a part of it.
We do not promise a takeover before the review. Sometimes the honest answer is “this is not worth saving”.
How do you work with our IT department?
On a shared repository and in one process: your team has access to the code, change reviews and the test environment from the first stage.
At the end — a handover session: architecture, deployment, how to diagnose errors in production. We write the documentation so that your team can develop the system without us.
Can we start with a small stage?
Yes — and we usually recommend it. The first stage is the analysis, or one integration or one process: a closed scope, a separate price, a working result.
We price the next stages after it, based on what already works rather than on assumptions made before the project.
Where is your team?
In Otwock, near Warsaw. We work remotely with clients from Poland, the European Union and Switzerland; in and around Warsaw we also meet in person.
NEXT STEP · THREE PATHS
Choose a path that fits where you are
I HAVE A SPECIFIC PROJECT
You know what you're building and need a quote
A web application with a defined scope: custom CRM, customer portal, B2B portal, internal dashboard, multi-tenant SaaS.
Describe your project →I NEED A CONSULTATION
You have a business problem and are looking for a technology architect
You know that your current tools (Excel, an off-the-shelf CRM, Zapier) are no longer enough, but you don't know whether the answer is a custom application, automation or a move to another SaaS.
Book a consultation →STILL WEIGHING IT UP
You want to understand the subject first
You are not ready for a quote or a consultation — you want to read about software development, compare approaches, and understand the difference between custom software and no-code/SaaS.
Guides and reports →
// 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
- We read your message and reply within one working day.
- We set up a short call about the scope, with no sales pitch.
- You get proposed stages and a price range.