Custom software · platforms

Custom software built around how your company actually works

Bespoke software development for processes that no off-the-shelf product covers without compromise.

When a company reshapes its process to fit the software, you end up with parallel forms, spreadsheets and duplicated work. We build it the other way round: the application is shaped around the way you already work.

We reply the same working day. No obligation.

A platform built to order: admin dashboard with reporting, source code, workflow builder and mobile app
12 years
building web applications
120+
projects delivered
8–16 weeks
typical platform timeline
3+ years
average client relationship
Situations

Three signs you need software of your own.

01

The process runs on spreadsheets

One shared file that several people open, multiple versions, formulas that break and nobody sure which copy is current.

An error in a shared spreadsheet is usually discovered after it has reached the customer.

02

You have a system, but you work around it

You use part of it, and the rest happens manually, because it does not cover what you actually need.

03

You have bought module after module

Every new requirement meant another extension. The system has become slow, fragile and hard to maintain.

Benefits

Exactly what you need, nothing more

No options nobody uses and no compromises imposed by a vendor.

Connected to your existing systems

The application does not live in isolation: it talks to stock, invoicing and the online store.

Built for your volume

Performance designed around the real number of users and records.

The code stays yours

No per-user licences and no dependence on a single supplier.

What you get

What a software project includes.

An internal application is judged by how quickly the team adopts it, not by how many features it has.

  • Analysis of the current workflowWho does what, in what order, with which documents and where the exceptions appear.
  • Functional specificationWhat the application does, for whom, with which roles and permissions. Written before the first line of code.
  • Interface prototypeYou see the main screens before development, so changes do not cost development time.
  • Development in modulesEach part is delivered working, so you can use the first components early.
  • Roles and permissionsWho sees what and who can change it, with an activity log.
  • IntegrationsConnected to stock, invoicing, payments, carriers or any system exposing an API.
  • Migration of existing dataWe take what you hold in spreadsheets or in the old system, cleaned and structured.
  • A test environmentYou verify on real data, with no risk, before going live.
  • Documentation and trainingA user manual and a session with the people who will work in the application daily.
  • Support after launchA period in which we adjust what only shows up in real use.
Types of project

What we build most often.

An internal process application

Managing a specific workflow: orders, production, scheduling, approvals, records. With roles, notifications and reporting.

8–16 weeks

A customer or partner portal

An account for each client or distributor: orders, documents, personalised pricing, history.

8–14 weeks

A booking system

Calendar, availability by resource, automated confirmations and integration with the team calendar.

6–10 weeks

A product configurator

The customer builds their product against real rules, and the result becomes a quote or an order.

8–14 weeks

A reporting dashboard

Data from several systems pulled into one place, showing the indicators you actually track.

4–8 weeks

Taking over an existing project

An application left without a developer or hard to maintain. Technical audit first, then an honest verdict.

after the audit

Process

Five steps, delivered in modules.

01

Process analysis

We spend time with the people who do the work, not only with those who describe it.

02

Specification and estimate

What the application does, by module, with estimated hours for each. You decide what goes into phase one.

03

Prototype and validation

The main screens, before development. Changes at this stage cost ten times less.

04

Iterative development

We deliver working modules along the way rather than everything at the end. You see progress and we correct course as we go.

05

Launch and stabilisation

Data migration, training, then a period of adjustment based on real use.

Technology

React and Next.js for the interface. PHP and MySQL where it makes sense.

We choose the stack based on what the application has to do and on who will maintain it, not on what is fashionable. Both directions are mature, well documented and easy for another developer to pick up.

Our stack

Modern web applications

The interface is built in React, with Next.js providing the application structure. The server side runs on PHP with MySQL or on Node, depending on the project and the existing infrastructure. Both options run on ordinary shared hosting or on a VPS, with no licence costs.

  • Interfaces that respond instantlyLarge tables, filters, multi-step forms and updates without reloading the page.
  • Roles and permissions from the startWho sees what and who can change it, with an activity log for audit.
  • Integrations without limitsAny system exposing an API can be connected: stock, invoicing, payments, carriers.
  • Performance at your real volumeCorrect indexing, optimised queries, asynchronous processing for slow operations.
  • No per-user licencesYou add people to the team without your monthly bill going up.
  • The code stays yoursYou receive it in full, with documentation. You can change supplier without rebuilding.

At Maramureș Padel Club we built the complete ordering and payment system: order from the table, pay on your phone with Apple Pay or Google Pay, and the order lands instantly on the kitchen screen.

Worth knowing: custom software costs more upfront than an off-the-shelf product. It is worth it when your process is a competitive advantage, or when the modules bolted onto a standard system would cost more than building it properly.

B2B portals

An account for every partner

Customer-specific pricing, quick ordering by product code, payment on terms, documents and history. It cuts the time spent taking orders by phone dramatically.

Suited to distributors and manufacturers selling to other businesses.

Applications with an AI component

An automated decision inside the flow

Triage, data extraction from documents, suggestions based on history. AI is one step in the application, not the product.

Suited when a repetitive decision consumes specialist time.

Record-keeping systems

What does not fit inside an ERP

Production, maintenance, equipment, contracts, approvals — specific workflows that general systems do not cover.

Suited when the process currently runs on shared spreadsheets.

Comparison of the technologies we use to build websites
Custom softwareOff-the-shelf productModules on an existing system
Fit to your processexactpartialpartial, with compromises
Initial costhighlowmedium
Cost over timemaintenanceper-user licencesmodules plus upkeep
Integrationsunlimitedwhatever the vendor allowslimited
Performance at volumeunder your controlvariabledegrades with each module
Do you own it?yesnopartly

Our rule: We do not recommend custom software when an existing product covers 90% of the need. We recommend it when the process is the company's differentiator, or when the modules bolted onto a standard system would cost more over three years than building from scratch.

Adoption

An application the team works around is a cost, not a tool.

The most common reason internal software fails is not technical. It is that nobody uses it, because it is slower than the old method.

Built together with the users

We talk to the people who do the work, not only to management.

Faster than the current method

If an operation takes longer than it did in the spreadsheet, we rebuild it.

Prototype before development

Screens are validated while a change costs minutes rather than days.

Training and documentation

Handover includes a session with the team who will use it daily.

The admin panel of an internal application developed by Divas

A concrete example: for Cabinero we built the calendar and booking system, with an AI assistant that triages the patient request and books the slot without an operator.

Projects

We do not promise. We demonstrate.

Platforms delivered and used daily by real teams.

View full portfolio
Project delivered by Divas Agency
Interface developed by Divas Agency
Platform developed by Divas Agency
Dr. Excel project developed by Divas Agency
Digital project developed by Divas Agency
Responsive project developed by Divas Agency

Frequently asked questions

How is the price set?

We work on an hourly rate: €50 per hour, excluding VAT. The price comes from the number of estimated hours rather than from a fixed package. You receive a proposal in which each module carries its estimated hours and cost.

How long does it take to develop an application?

An internal process application takes 8–16 weeks. A customer portal takes 8–14 weeks. We deliver in modules, so the first components can be used before the whole system is finished.

What technologies do you use?

React and Next.js for the interface, PHP with MySQL or Node for the server side, depending on the project and the existing infrastructure. Integrations over REST and SOAP, plus AI APIs where an automated decision is needed. We choose based on what the system has to do, not the other way round.

Do I own the code?

Yes, in full and with documentation. There are no per-user licences and you do not depend on us to continue. You can move the project to another developer at any time — which is a further reason for us to write clean, documented code.

Where is the application hosted?

On your existing hosting, on a VPS or on cloud infrastructure, depending on volume and security requirements. The recommendation follows once we have estimated traffic and data volume.

Can we start with a smaller version?

Yes, and that is usually what we recommend. We build the module with the greatest impact, put it into production and validate it with real users. The rest follows based on what we learn in use.

What happens to the data we currently hold in spreadsheets?

We migrate it. We take the files, clean the data, structure it properly and import it. It is a separate stage in the proposal with its own hours, because the duration depends heavily on the state of the data.

Will you take over an application started by someone else?

Yes. We start with a technical audit: what is written cleanly, what is risky, and what continuing would cost against rebuilding. We give you the honest verdict, even when it means we are not the ones continuing.

What happens after launch?

We stay on for support and continuous development. An internal application changes as the process changes, and the first weeks of real use always surface useful adjustments.

Estimate

Tell us what you need. We reply with an estimate.

Five steps, under two minutes. The more context you give us, the closer the estimate will be to reality.

ProjectStep 1 din 5

What would you like us to build?

You can pick more than one.

Describe your process to us.

You do not need to know which technology suits you or what the application should look like. Tell us how you work today and where time is lost. We reply with the structure we propose and the estimated hours for each module.

Get an estimate

Or email us directly: contact@divasweb.ro+40 755 336 514

Get a quote