Bespoke software and application development

Qomanda. Built and operated by Alture.

Qomanda is our restaurant booking software, available at app.qomanda.es. We built it and manage its payments, notifications, updates and support.

Staff manage bookings, the floor plan, guests and services. Diners book through the restaurant’s website, in its own identity and in twelve automatically detected languages.

The product runs on Next.js, React, TypeScript and Postgres, with Supabase, Vercel and Stripe. It costs €49 per month per restaurant, with no per-diner commission and a thirty-day trial without a card.

You can visit qomanda.es, check the price and try the product before our first meeting.

Design for failure as well as success

A booking illustrates our approach: check availability, capacity and the table before confirming. If two people request the last slot, the system must resolve it without creating a duplicate booking.

In Qomanda these rules live in the database. For a custom project we similarly define permissions, concurrent operations and failure handling. We agree on behaviour before building the screen.

The app your customers book, order or buy through

Booking, making an appointment or buying should feel simple from the first use. We design clear journeys with few steps and language your customer understands.

Qomanda’s booking engine fits into the restaurant’s website, adopts its identity and detects twelve languages. The business chooses which information to request; confirmations and reminders go by email.

The customer relationship stays with your business. Their details and history remain part of your own customer database.

Your operation, connected.

Work orders, shifts, inventory and traceability. We build screens for real working conditions: standing, moving and making decisions quickly.

In Qomanda, operations change throughout service: bookings, orders and stock. That experience provides a foundation for studying the specific needs of your process.

Qomanda’s operations module connects orders, the touch terminal and a live kitchen display. It includes recipe costing and waste, stock deductions at payment, purchase notes with weighted average prices, consumption reports and cash reconciliation.

Sales documents retain consecutive numbering by series and a chain of signatures. Cash reconciliation preserves the recorded totals, and reprints retrieve the same document.

This module is enabled case by case with assisted setup. Configuration and operation are reviewed before it becomes part of the service.

Every booking and order in its place.

Two people may try to book the last table or sell the last item at the same time. We design the rules to keep information consistent when that happens.

In Qomanda, the database checks capacity, availability and the table before confirming a booking, in one operation. Further checks prevent overlaps when bookings are created or reassigned.

These checks protect the team’s work as activity grows. Bookings, tables and availability keep following the same rules.

If your app takes payments, the money goes into your account

Customer payments go to your own account. We establish that decision at the start of the project.

Qomanda uses Stripe Connect with direct charges. The account belongs to the restaurant and the amount reaches its balance, without Qomanda holding funds.

The restaurant can save a card, hold an amount or charge a deposit. We assess the same type of integration for subscriptions, one-off payments and booking deposits. Processing fees are paid to the payment provider.

Each person gets the access they need.

Qomanda separates each restaurant’s information within the database itself. Access rules protect the data across the application.

Five roles —owner, manager, floor, waiter and read-only— define what each person can do. Invitations arrive by email, and support access is logged with a visible notice.

The restaurant can enable guest anonymisation after its chosen retention period. Operational booking, occupancy and billing records are retained.

Qomanda’s servers and functions run in Frankfurt. Booking, customer and invoice exports remain accessible when the subscription ends.

A team behind you, beyond launch.

An application still needs attention after launch. We monitor automated processes and alerts to detect issues and act on them.

Qomanda has seven automated processes: reminders, end-of-day closing, surveys, a safety net, billing health, data retention and monitoring. The system alerts us if a process stops running.

Server alerts help us identify incidents. We also check that the deployed code and database match the intended version.

Development, monitoring and support for your application are covered by a monthly fee. The same team looks after daily operation and the changes ahead.

Know what is ready. And what comes next.

In Qomanda, planned features are labelled “Coming soon”. Available features are ready to use.

Every screen reflects the state of the product. The team can work knowing which actions are ready.

In your project, each phase has a defined scope. You see what is delivered and what will be developed next.

Mobile app, web or PWA: the right format.

We choose the format around where the application is used, what it needs to do and who will use it.

A web application can open on mobile, tablet and desktop. As a PWA, it can be installed on the home screen where supported. Qomanda uses this approach for its touch terminal.

We consider native development when you need device features, offline operation or an app-store presence. We compare capabilities, cost and maintenance before deciding.

Which applications do we build to order?

Bookings, appointments and registrations. Availability, shifts, capacity, confirmations and reminders, with a custom engine or the system you already use.

Customer portals and private areas. Orders, documents, records and invoices, accessible according to each user’s permissions.

Operations dashboards. Data from different tools brought into one screen to follow activity and make informed decisions.

Touch terminals and field applications. Screens for taking orders, closing work reports or recording warehouse deliveries in real working conditions.

Integrations and automation. We connect ERP, CRM, invoicing, payments and email through their APIs to reduce duplicate tasks.

Your own software product. Applications serving multiple businesses, with subscriptions, customer signup, administration and billing. This is the architecture we built for Qomanda.

First versions and ongoing development. We validate an idea with the essentials or take over an existing application after reviewing what to keep and improve.

From your real process to the first version.

We understand the process, organise the data and build a first version. We test it with the people who will use it and develop it around their experience.

When the application supports a physical operation, we visit it. Seeing who performs each task and under what conditions helps define the software.

We define states before designing screens. A Qomanda booking has fifteen, covering the journey from pending to completed or cancelled. Each reflects a real service situation and the actions available.

We launch the essentials first and observe real use. You approve each phase and help prioritise the next.

Custom app development in Madrid and across Spain

From Madrid, we work with companies across Spain. You have a dedicated contact and regular reviews.

If the project depends on a dining room, factory or warehouse, we visit at the start. The same team then stays with you through development and operation.