SOFTWARE HOUSE · OTWOCK / WARSAW
About dvnt
We design, build and maintain software for small and medium-sized companies: applications, integrations, automation and AI. We start from the goal and the outcome, and only then choose the technology.
We respond within 24 hours on business days. Talk via Google Meet or phone - you choose. After the conversation, we do not pursue emails; if you do not write further, we close the topic.
Goal first,
technology second.
Custom software is expensive when it is built without a plan. That is why the price of each stage is known before it starts, and the code sits in your repository from day one.
// How we help
How we help companies.
We support small and medium-sized companies in Poland and the EU that want to put their tools in order, speed up processes or build a system that fits them.
02 · INTEGRATIONS
Integrations and automation
ERP, CRM, KSeF and processes that live in spreadsheets today.
How we work
A simple, controlled process.
We want technology to genuinely strengthen your business.
Diagnosis
We gather context: business goal, constraints, current solutions and major bottlenecks. If necessary, we do a quick audit (e.g., of the site, process, tools) and determine where the fastest effect will occur.
Plan
We translate the goal into an action plan: priorities, scope, implementation options and risks. You get recommendations: what to do now, what to postpone, and how to approach the topic in stages so you don't get stuck in dead ends.
Implementation in stages
We implement the project in stages, with clear checkpoints and transparent communication. As a result, you can see results faster, and the scope and costs are under control.
Team and expertise
Konrad Barejko
Over 20 years in IT, including projects for clients in many countries and at scale. We are responsible for a predictable process: diagnosis, plan, delivery in stages.
We deliver projects as a team, choosing specialists for the goal, scope and risks. On your side there is one contact person from start to finish.
- in IT and B2B, EMEA
- 20+ years
- working languages
- PL · EN · FR
- infrastructure in Warsaw
- EU
// security · no spin
What we promise and what we do not
In projects with an SLA
A plan for an outage
A concrete document: what we do in the first 15 minutes of an outage, who calls whom, what the RTO and RPO are.
Honestly
We are not ISO 27001 certified
We do not run quarterly penetration tests as standard. If your industry requires it (finance, health), we will say so plainly and find a solution.
FAQ · 8 questions
Frequently asked questions.
Where do we start our cooperation?
From15-minute conversation without obligation. You talk about the goal, the current situation and bottlenecks. We ask questions to understand the context - industry, scale, constraints.
After the interview you getclear direction: what to do first, what can wait, how to approach the topic in stages. If the topic can be solved more simply or does not fit into our specialty - we will tell you directly.
How long does a typical implementation take?
Depends on the scope, but in practice:
- Company website: 4-8 weeks
- E-commerce store: 8-16 weeks
- Web Application / MVP: 12-24 weeks
- Process automation: 2-6 weeks
- Audit + plan: 1-2 weeks
We give a timeframe after diagnosis, not before. We divide the implementation into stages with clear checkpoints - the first results are usually seen after 4-6 weeks, even for large projects.
How do we account for the work?
In stages, not upfront for the whole thing. Typical structure for a 3-month project:
- Advance payment to start the work (diagnosis + plan)
- Payment after each milestone (usually 2-4 checkpoints)
- Last installment after launch and stabilization period
VAT invoices, transfer 14 days. For long-term projects (IT support, application development) we use a monthly subscription with a clear scope. We do not work in a "pay 100% upfront" model - you also bear the risk only in stages.
What happens if you change the scope during?
Normal thing - in 60% of projects the scope evolves after the first milestone. We don't invoice change requests in a hidden way.
What it looks like in practice:
- Minor changes in scope (e.g., text change, additional section) - fit within existing budget
- Changing functionality (e.g., adding integration with a new system) - you get a quote before the work starts, decide whether to add to the scope or put it off for later
- Fundamental change of direction - back to Plan stage, re-prioritize scope together
Transparency > rigid adherence to the original contract.
Who will work on my project?
First conversation - with Konrad (founder, 20+ years in IT). Not with an SDR, not with a salesman. You are talking to someone who will be responsible for your project.
We carry out the implementation as a team - we match specialists to the scope and risks:
- Strategy and product - Konrad + product lead
- Design and UX - designer with experience in the industry (SaaS, e-commerce, B2B)
- Development - seniors and mid-devs; no juniors on your project
IT and DevOps support - dedicated post-launch mentor
In practice: 2-4 people per project, constant contact with one person on your side.
How are you different from a typical software house?
Some specifics:
- We start from the goal and a diagnosis, not from a team for hire. The price of each stage is known before it starts.
- We say so when an off-the-shelf tool will do — we do not build custom code for its own sake.
- The code and the decision records are in your repository from day one, with no lock-in.
- One contact person from start to finish; we choose specialists for the project.
- Infrastructure in the EU (GDPR), VAT invoices, work in Polish and English.
We are not for everyone: a multi-region project with 24/7 support is better done by a larger software house — we will tell you in the first call.
Will you sign an NDA? Is the data safe?
Yes on the NDA - standard, before giving us sensitive business data. We also have a ready-made template if you don't have your own.
Safety in practice:
- Our own infrastructure in the EU - data does not fly to the US unless there is a business need.
- GDPR compliance as standard - as a controller of data processors
- SSL on all deployments
- Isolated dev / staging / production environments
- Backups and disaster recovery plan for projects with SLAs
- Controlled access - each team member sees only the data they need
For regulated industries (finance, health) - we expand with additional audits.
What happens after the launch?
The first 30 days - the stabilization period in the price of implementation. We monitor bugs, fix small things, observe how the user and server behave.
Long-term - you choose the support model:
- Ad-hoc - you pay for specific changes (new section, integration, update). No monthly commitments.
- Retainer / SLA - monthly subscription with a certain number of hours, priority of requests, dedicated supervisor.
- Development roadmap - quarterly implementations of new features (for projects that are growing with the company).
If you do not need support - we have no images. The site is designed to work on its own. You come back when a new need arises.
Cooperation and partnership
A technology partner for agencies.
We work with marketing, branding and IT agencies: subcontracting applications and integrations, working under your brand, ongoing cooperation. The partner programme covers referrals too.
// For agencies
Tell us what you are building. We come back with a plan.
A client project that goes beyond a website: an integration, a panel, an app. Describe it and we send back a delivery plan.
What happens next
- We reply within one working day.
- We agree the scope and how we work with your team.
- We come back with a plan: stages, dates and a quote.