Skip to content

What we build

Tailored software development

When it is worth having custom software written and when it is worth buying, told by the people who write it: how long it takes, what it costs, who keeps the code.

Let’s talkSee all projects

Where we have already done it

When is custom software worth it instead of a market management system?

When your way of working does not fit a market product, and bending it would cost more than writing it. Sometimes nothing needs replacing: if a procedure goes through five programs, an app can call them all. If the process is the same as everyone’s, like accounting or payroll, we tell you to buy.

Tailored software adapts to your workflows, not the other way round.

Building tailored software gives you a solution designed around your needs, better suited and more effective than a generic commercial product.

Tailored software

What it is

Tailored, or custom, software is an application developed for the needs of a client or a company. Commercial software is designed for a broad audience, with a standard set of features; tailored software is built on request, for specific requirements.

Not every company has the same needs. An off-the-shelf product is quicker to adopt, but it may not fit the specifics of your work: that is where tailored development comes in.

Five reasons to choose it

  • Fitted to your needs

    Listening, integration and customization to reach your company’s goals.

  • Flexibility and scalability

    It adapts as your work evolves and lends itself to changes and extensions.

  • Security and control

    The source code is yours: you can have more specific protection for sensitive data.

  • Integration with other systems

    With full control of the software, it connects easily to an ERP or CRM.

  • Competitive advantage

    A tool that sets you apart from competitors and helps you adapt to the market.

The process

How we develop it

  1. Analysis

    It starts with listening. We organize meetings and a study of the context the software will be used in, and we set its features and timeline.

  2. Design

    The structure and design of the software, based on the analyzed requirements: the “what” is linked to the “how”. Feasibility and requirements studies anticipate problems.

  3. Development

    Prototyping first, to define the parameters; then every stage of development, from choosing the language to the appropriate technologies.

  4. Testing

    Testing checks compliance with the requirements and correct operation, with unit, integration and functional tests.

  5. Release

    The complete software, with documentation and instructions to install and use it: release notes, updated manuals, installation support and data migration.

  6. Maintenance

    Changes after release: fixing errors, adapting the software to new environments, extending its features.

Your project: we help you

From the first consultation to release and maintenance, you are always kept up to date on progress. A complete team works on the project.

  • Project manager
  • Developers
  • UX/UI designer

What happens if it goes wrong?

Guarantees

Frequently asked questions

Who owns the source code?

You do. Source, documentation and development environments are your property, and they stay yours even if one day you change supplier.

How long does a project take?

Months, split into phases. Each phase has a date and ends with a system running on real data: looking at that is how you decide what to do in the next phase.

Does it integrate with the ERP we already have?

Yes. For a manufacturing company with several plants, for example, we wrote a web app that runs the production lines and talks to an AS400 through APIs.

How much does custom software cost?

A custom project lasts months and costs tens or hundreds of thousands of euros. The range is wide because the scope and the integrations vary a lot from one company to another, and that is why we go and look at them before giving a number.

How do you choose a supplier of bespoke software?

Ask who will write the code, the people from the first meeting or others; who will own the source at the end; and whether the work is split into phases with a date and a result you can check. More questions to ask are in «The 10 questions to ask a software house».

Does it work for a company with several sites too?

Yes. The hard part is knowing where the identity of whoever logs in comes from. For a company with 1,200 employees and sites around the world, access went through several LDAP directories on different Active Directory instances. In the app we wrote, whoever requests a business trip and whoever approves it do not see the same things.

Who maintains the software after release?

We do, if you want, with a paid agreement for ongoing maintenance, and with guaranteed response times if you need them. Defects in the software we deliver we fix at our own cost, under the legal warranty. If one day you prefer to hand it to another supplier, code and documentation are already yours.

Tell us about the project you have in mind.