Custom Apps & Dashboards

Custom apps and dashboards, built around how you work.

The tool your business needs, when nothing off the shelf fits: a booking app, a check-in form, a client dashboard or a mobile app.

Some work does not fit a plugin. Your staff need one screen for the day’s bookings. Your guests should check in from their phone. Your clients want to see their numbers without asking you for a report. We build that, on your own domain, and we explain every step in plain words.

For hotels, restaurants, associations, non-profits and growing businesses with a process of their own.

Development at €100 an hour · Web apps, dashboards, and iOS and Android apps.

Today

Example

  • Bookings today18
  • Checked in7
  • Waiting3

Illustration of the kind of screen we build.

  • €100 an hourdevelopment, billed by the hour
  • Web, iOS and Androidone team for all three
  • Your own domainapp.yourdomain.com or yourdomain.com/booking
  • 25+ yearsof web experience behind the work

In short

Sfida.PRO does custom app development: web apps, mobile apps and dashboards for businesses and organisations. Development costs €100 an hour, and the total depends on how many hours your tool needs. We start by checking whether you need a custom build at all, because a form, a booking plugin or an app you can already buy is often enough. When it is not, we build exactly what your team and your customers need, and we keep it simple enough for your staff to use on day one.

  • What we build: booking apps, check-in and registration apps, client dashboards that join several data sources, and mobile apps for iOS and Android.
  • What it costs: €100 an hour for development. The scope is agreed in writing before work starts.
  • Where to start: tell us what you do today and what is slowing you down. We answer with a plain “yes, build it” or “no, you do not need to.”

Do you need an app at all? Often, no.

We would rather tell you that a simple tool is enough than sell you a build you do not need. Try these first.

A form that emails you

If people only need to send you details, a form on your site does it. We use Fluent Forms for this on many sites.

A booking plugin

If you take appointments or calls, a booking plugin handles the calendar, reminders and payments. We run one ourselves on our own call-booking page.

A shop plugin

If you sell things, WooCommerce or FluentCart already does carts, payments and orders.

An app you can already buy

For a standard need, such as invoicing or a mailing list, a ready-made product is cheaper than a build.

Build custom when your staff need a working screen of their own with roles and history, when your data lives in several places, or when your rules are specific to you. That is when we start the clock.

We once looked at building a booking app for local sports clubs. We found the clubs were already listed on two booking apps. What they lacked was players using them, not more software. So we did not build one.

What we build

Four kinds of tool, each with a real example below.

Bookings

Booking and reservation apps

A page where customers book a table, a room, a class or a slot, and a staff screen where your team confirms, moves and tracks every booking. Staff sign in with their own login, so every change shows who made it.

Check-in

Check-in and registration apps

A form your guests, visitors or event attendees fill in from their phone, often by scanning a QR code. The details go straight to the people and systems that need them: reception, your CRM, your team’s inbox.

Dashboards

Client dashboards

One clear screen that pulls numbers from several places and shows them in a way your client or your owner understands at a glance. No spreadsheet, no waiting for a monthly report.

Mobile

Mobile apps for iOS and Android

When your users need an app on their phone, we build it. Before we do, we ask one question: would a web app that opens from the phone’s home screen do the same job for less? Often it does. When it does not, we build the native app.

Examples from our own work

We have built booking, check-in and dashboard tools for a hotel and a business chamber, and a payment system for a foundation. These are real projects, with what we built and what we know about how it is going. We only give numbers we can show.

Hotel in Tirana · Reservations

A restaurant reservation system for a hotel

The problem. The hotel’s restaurants, rooftop and bar took bookings by phone and in a WhatsApp group. The team needed one list of the day.

What we built. A public booking page in Albanian and English for six venues, and a staff board where the team sees the day, confirms and moves bookings, notes VIP guests and sends a ready-written WhatsApp confirmation in one click. Staff sign in with a one-time code sent to their email, and managers and reception have different rights.

How it is going. Built and checked by 75 automated tests. It is running in test mode, so it takes no real bookings yet. The hotel has asked for down payments, WhatsApp confirmations and hotel-guest recognition next. Those are planned, not built.

Built with: Cloudflare Workers, a Cloudflare database in the EU, Cloudflare Access for the staff login.

Hotel in Tirana · Check-in

A guest check-in form that feeds the front desk

The problem. Bookings from travel sites such as Booking.com do not give the hotel the guest’s real phone number or email. Reception had a name and sometimes a relay number.

What we built. A check-in form the guest fills in on their phone. On submit it emails reception, creates or updates the guest in the hotel’s CRM, and passes the details to the hotel’s guest-messaging service. Reception adds the room number, because a guest should not have to guess it.

Result. The form is now the hotel’s source for guests’ real phone numbers and emails. The welcome-email sequence it starts sent 507 emails in October 2026.

Built with: Fluent Forms, FluentCRM, a webhook to the messaging service.

Business chamber in Tirana · Events

A QR check-in for events

The problem. At every event the chamber’s team needed the attendees’ details without paper lists, and the data needed to land in the member CRM.

What we built. One short form (name, email, position, company), opened by scanning a QR code. Each event has its own QR code, which tags the attendee for that event in the CRM. Every three hours the office gets one email listing who registered.

Result. Tested end to end with three real submissions: a first-time visitor, a repeat visitor and a visitor with no event. Testing found that the obvious QR link word is reserved by the chamber’s site and would have shown every guest an error page at the door. We changed it before any event used it.

Built with: Fluent Forms, FluentCRM, a short custom script for the digest.

Hotel in Tirana · Dashboard

A daily market dashboard for a hotel owner

The problem. The hotel wanted to know how its room prices compared with its competitors, night by night, without someone checking websites by hand.

What we built. A dashboard, behind a login, with prices for the hotel and 11 competitors for each of the next 365 nights. A daily job refreshes it, taking prices from a price feed and review scores from TripAdvisor. Filters cover competitor group, period, weekdays and weekends, and “only nights where we are not the cheapest”. Every day’s data is kept, so next year the dashboard can compare with this year.

Result. The first full-year run checked 4,380 prices (365 nights, 12 hotels) in about 81 minutes, with no errors. The dashboard has been live since 17 October 2026.

Built with: a hotel price feed and TripAdvisor ratings.

Business chamber in Tirana · Dashboard

A members dashboard inside the CRM

The problem. The chamber was moving off a paid membership platform and needed its key numbers in the CRM it now owns.

What we built. A read-only dashboard page inside the CRM. It shows members by tier and role, contact statuses and the newsletter list, with data gaps flagged. For newsletters it shows results next to the old platform’s results (34% opens, 2% clicks, 1% bounces), so the chamber can see whether the new setup does as well. Member participation figures from its own report sit beside them.

Result. Live since 29 October 2026. It reads the CRM directly, so the numbers are current when someone opens the page.

Built with: the member CRM (live) and the chamber’s participation report (January to August 2026).

Foundation · Payments

A donation and camp-registration system for a foundation

The problem. The foundation wanted to take donations and summer-camp places online, in Albanian, English and French, and settle in Lek through a local gateway.

What we built. A donation page with free-choice amounts, camp places with a two-payment option, a form for each child, confirmation emails in the donor’s own language, and payments through a local Albanian gateway.

Result. Live on the foundation’s site.

Built with: WooCommerce, WPML, a local payment gateway.

How a project runs

Five steps. You see something working early, and you decide at each step whether to go on.

Talk and check

A free call. You tell us what you do today and what is slowing you down. We tell you honestly whether you need a custom build.

Scope in writing

We write down what the tool does, who uses it and what it connects to, with an estimate in hours for each milestone. Custom projects run on a short Statement of Work with milestones (Terms, sections 4.4 and 13.2).

Build in small pieces

We build the core first and show it to you early, so you can say “yes” or “not quite” while it is cheap to change.

Test before go-live

We run the tool in test mode first, with your staff, so nothing real goes through until it works. A hotel’s reservation system we built is running exactly like that now.

Launch and look after

We go live together, show your team how to use it, and agree how the tool is looked after afterwards. If the tool needs a new website or hosting around it, we can build and look after that too.

Who owns what. You own the custom code we write for you once the invoices are paid. We keep our reusable parts and tools, and may use them again. Your own records, such as guests, bookings and members, are always yours.

What it costs

Development is €100 an hour. There is no package to decode. You pay for the hours your tool needs, and the scope sets those hours.

The sum that helps you decide. Divide the build cost by the hours it saves each month. If a tool saves your team 20 hours a month and a staff hour costs you €10, it returns €200 a month, and a €2,000 build pays itself back in ten months. These are made-up numbers to show the sum, not a quote. Bring your own and we will do the sum with you.

All prices exclude VAT.

Development

Custom development

For web apps, dashboards, integrations and mobile apps.

€100/hour

  • A written estimate in hours for each milestone, before work starts. It is an estimate, not a cap.
  • We tell you the moment the scope changes, before the extra hours are spent. You approve any extra hours.
  • Outside costs, such as message fees, payment fees and hosting, are named in the scope.
  • After launch, fixes to what we built are support hours at €50/hour (prepaid blocks apply). New features are development at €100/hour.
  • You own the custom code once the invoices are paid.

What drives the hours

People and roles

One staff screen is simpler than customers, staff and managers each seeing something different.

Connections

Each system your tool talks to adds work: a CRM, email, WhatsApp, payments, a data feed.

Money and messages

Payments, deposits and message confirmations take more care than a plain list.

Languages

An Albanian and English tool costs more than a one-language tool.

Existing data

Moving old bookings, guests or members into the new tool takes time.

Testing and polish

We test with your staff before go-live. That time is in the scope.

Questions, answered

Do I need a custom app, or will a plugin do?

Often a plugin does. A form, a booking plugin or a shop plugin covers most simple needs for much less. A custom build makes sense when your staff need their own working screen, your data lives in several places, or your rules are specific to you. We tell you which side you are on before you spend anything.

How much does a custom app cost?

Development is €100 an hour. The total is the hours your tool needs, and those depend on people and roles, connections, payments, languages and data to move. We agree the scope in writing first, with an estimate in hours for each milestone.

Do you build mobile apps for iOS and Android, or web apps?

Both. We start with a web app when it does the job, because it works on every phone without an app store. When you need something only a native app can do, we build it for iOS and Android.

Can the tool live on my own website or domain?

Yes. It can sit on a page of your site, or on a subdomain such as app.yourdomain.com. A hotel’s reservation system we built, for example, runs on its own subdomain and looks like part of the hotel’s brand.

How do my staff sign in?

Each person has their own sign-in, so every change shows who made it. In that hotel’s reservation system, staff get a one-time code by email, with different rights for managers and reception.

Can it connect to the tools we already use?

Usually. We have connected tools to a CRM (FluentCRM), website forms (Fluent Forms), email sending, a local Albanian payment gateway, Google data, price feeds and reservation exports. Tell us what you use and we will say what is possible.

Who looks after it after launch?

We do. We agree how the tool is looked after before launch, so you know who to call and what it costs. Fixes to what we built are support hours at €50 an hour, and prepaid blocks apply. New features are development at €100 an hour. Hosting and running costs are agreed in the scope.

Who owns the code and the data?

You own the custom code we write for you once the invoices are paid. We keep our reusable parts and tools, and may use them again. Your records, such as guests, bookings and members, are always yours, and you can ask for an export of your content (Terms, section 17).

Request a custom app

Tell us what you need.

Describe what you do today and what is slowing you down. We reply with a plain answer: whether you need a custom build, what we would build and how we would scope it.

  • A reply with an honest answer, even if the answer is “use a plugin”
  • Scope and milestones in writing before work starts
  • Development at €100 an hour

Prefer to talk first? Book a free call →

Custom apps: request

Prices valid from 6 November 2026.

Scroll to Top