Build software around the workflow standard products cannot support.

Custom development is justified when the differences matter.

Standard products are the right answer for many requirements. The difficulty begins when important work depends on repeated workarounds, manual transfers, missing integrations or compromises that affect customers and operations.

We first determine whether the requirement is genuinely distinctive. If an existing product can meet it well, we will recommend that path. Otherwise, we define the smallest custom solution that creates meaningful value.

Signals:

• →Several tools are required to complete one process.
• →Important edge cases cannot be configured safely.
• →Data must move between internal and external systems.
• →The organization needs control over roadmap, operation or ownership.
• →A customer or employee experience is limited by the current platform.
• →Existing software creates more manual work than it removes.

The workflow before the feature list.

Requirements become clearer when they are connected to users, decisions, data and exceptions. We map how the work happens today, where it varies and what must remain possible as the organization grows.

Discovery covers:

• →Users, roles and responsibilities
• →Current workflow and exceptions
• →Data sources and ownership
• →Required integrations
• →Security and access
• →Operational and regulatory constraints
• →Expected usage and scale
• →Maintainability and support
• →Measures of success

What we can deliver

• Web applications

  Customer portals, operational platforms, administration systems, dashboards and workflow applications.

• Mobile applications

  Mobile products and internal tools designed around field work, customer access or operational use.

• Internal business systems

  HR administration, internal IT, finance, document, request and reporting workflows.

• Commerce and operational software

  E-commerce, retail, logistics, vending and software supporting physical operations.

• Integrations and data services

  APIs, middleware and reliable data exchange with existing platforms and external systems.

Build the smallest useful system, with room to grow.

• Define the first valuable outcome

  We identify the part of the problem worth solving first and the result that would justify the investment.

• Make architecture choices explicit

  Technology decisions are connected to usage, security, integrations, team capabilities and expected change.

• Deliver working increments

  Real use reveals more than a long specification. We develop in stages that can be reviewed and tested.

• Design for operation

  Monitoring, documentation, deployment, backup and failure handling are considered before launch.

Start with a discovery and scope package.

Before a larger build, we can define the problem, the first release and the decisions that influence cost and risk.

Deliverables:

• →Process and user map
• →Requirements and priorities
• →Integration and data map
• →Key risks and open decisions
• →Architecture options
• →Recommended first release
• →Indicative roadmap and investment range

Relevant experience

The experience behind Solandrix includes custom software for commerce, retail, logistics, healthcare, pharmaceuticals, finance, vending, HR, internal IT and integrations with systems in the public sector. It also spans web and mobile engineering, cloud platforms, IT operations and DevOps.

Frequently asked questions

When is custom software worth it instead of an existing product?

When important work depends on workarounds, manual transfers or integrations a standard product cannot provide, and the difference affects customers or operations. If an existing product meets the requirement well, we recommend it. That decision is made in discovery, with the trade-offs written down.

How long does custom software development take?

A discovery phase usually takes 1-2 weeks. A first working version typically follows in 6-10 weeks, depending on integrations and how much is still unknown. Larger systems are then delivered in further increments.

How much does custom software cost?

Cost depends on scope, integrations, data quality and how the system will be operated. After discovery you receive an estimate for each phase and an investment range, so the decision to build is made with the numbers in front of you.

Who owns the code?

Your organization does. The code, documentation and project accounts belong to you, and you remain free to run the system internally or with another provider.

Do you work with companies outside Bucharest?

Yes. Solandrix is based in Bucharest and works with companies across Romania and, remotely, across Europe. Most of the collaboration runs online, so location does not limit the project.

What do we need to prepare before we start?

A short description of how the workflow runs today, who uses it, which systems it touches and the result you want. The full specification comes out of discovery.

Proof and further reading

• Guide

  Oct 2026

  AI-built internal tools: keep, replace or rebuild?

  Your team built a tool with AI and now part of the business runs on it. How to decide who owns it, and whether to keep, replace or rebuild it.

  Read the article→
• Guide

  Sept 2026

  What a vibecoded prototype still needs before it can run a business

  AI tools can turn an idea into a working app in a weekend. Here is how to tell what can stay, what can wait through a pilot, and what must be fixed first.

  Read the article→
• Project

  Sept 2026

  Octodoc: from a complex requirement to a live telemedicine product

  Solandrix brought the technology, Octodoc the business vision - together, a telemedicine product for communities with limited access to medical services.

  Read the article→