FutureDesk Spain Launch Plan

01Summary

FutureDesk already exists and runs every day inside FutureDesh. It covers attendance, leave, work planning, projects, requisitions, salary records, announcements and more. We now want to sell it to other companies, starting in Spain.

We will not sell a shared online subscription. Each client gets their own installation on their own server. Their employee data never leaves their server, and they pay once for the software instead of paying per employee every month.

First market

SpainSMEs, 20–250 staff

Year-one target

20 clientssigned and installed

Pricing

≈ $5,000one-time + $300 / month

Market-ready

Feb 2027pilots in January

02The product

Every module below is built and in daily use. Clients can switch off modules they don't need.

03Why Spain, and how we compete

Why Spain first

• A local partner. We have a direct connection in the Spanish market, which matters more than anything else for a first market.
• A legal reason to buy. Since 2019, every Spanish company must record each employee's daily working hours (registro de jornada), keep those records for four years, and show them to the Labour Inspectorate on request. Many small companies still do this on paper or in spreadsheets. Our attendance module already does most of this.
• Privacy-conscious buyers. GDPR makes many companies uneasy about putting employee data in someone else's cloud. Our "your own server" model answers that directly.

The competition

Spain already has strong HR software companies, including Factorial, Sesame HR and Woffu. They mostly sell online subscriptions priced per employee per month. We are not trying to beat them on features. We offer a different deal:

Best-fit clients: companies with 20 to 250 employees, where a per-employee subscription becomes expensive, or which care about data control (for example healthcare, legal, finance, manufacturing), or which have processes that standard software doesn't fit.

04Business model

At the year-one target: 20 licenses ≈ $100,000 one-time revenue. Twenty clients on maintenance ≈ $6,000 per month ($72,000 per year) in recurring revenue. Clients will sign over the year, so actual first-year income will be lower than these totals.

Rules that protect the business

• No maintenance, no updates. Clients who stop paying keep the version they have, but get no updates, fixes or support. We support only the two most recent versions.
• Custom work is paid and goes into the main product. Every customisation becomes a setting in the one shared product. We never keep a separate copy of the code for one client. This is what lets a small team maintain 20 clients.
• Maintenance has clear limits. The contract states exactly what $300 covers (updates, backups, fixes, a set number of support hours) and what it doesn't (new features).
• Prices for Spain to be set in euros. The figures above are working numbers in US dollars. The final euro pricing should reflect what the partner learns from Spanish buyers.

05How clients get it

Each client has a completely separate installation. Nothing is shared between clients.

Only technical health information (online status, version number, backup result, error reports) travels back to us, with the client's agreement in the contract. Employee data stays on the client's server.

Installation, step by step

1. The client buys a Hostinger VPS in an EU data centre using our recommended plan, or we provide one under managed hosting.
2. We run one install command. The full system is running on the client's own web address with HTTPS in about 15 minutes.
3. We set up the company: logo, departments, users, Spanish holidays (national, regional and local), leave types and working hours.
4. We train the client's admin staff, and employees receive email invitations to set their passwords.
5. Monitoring and nightly backups switch on automatically.

06Making it Spain-ready

The product was built for one company in Bangladesh. These are the changes Spanish clients need.

07Technology changes

We are deliberately not rewriting the product. The core technology is modern and widely used. The changes are about packaging, security, compliance and maintainability.

Current foundation (kept)

React web app (works in any modern browser, desktop or mobile) · Node.js application server · MongoDB database · live notifications over WebSockets. These are mainstream technologies used by thousands of commercial products. Developers are easy to find, and they will receive updates for years.

What changes

Planned for after launch

These improve the code for the long term but aren't needed for the first clients. We will do them gradually after February:

• Moving the code to TypeScript (fewer errors as the team grows).
• Modernising how the web app loads and caches data.
• Single sign-on with Microsoft or Google accounts, for larger clients.
• A mobile app, if clients ask for one (the web app already works on phones).

08Maintenance and support

Maintaining many separate installations is the main operational challenge of this model. This is how we keep it manageable.

One product, many servers

Every client runs the same software. Differences between clients are settings, never separate code. A fix made once reaches every client.

How an update reaches a client

1. We release a new version after automated tests and upgrade tests pass, normally once a month and immediately for urgent security fixes.
2. The update agent on the client's server backs up all data and files.
3. It installs the new version and upgrades the database automatically.
4. It runs a health check. If anything fails, it restores the previous version on its own.
5. The result appears on our monitoring dashboard.

What we see centrally

For every client: online or offline, version, last backup result, disk space, and error reports. Problems trigger alerts to us, so most issues are fixed before the client reports them.

Proposed support levels (draft)

Our team is in Bangladesh, 4 to 5 hours ahead of Spain, so the full Spanish morning overlaps with our working day. Support should be available in Spanish, either through a team member or through the partner for first contact.

09Roadmap to February

From 6 October 2026 to launch at the end of February 2027. No new features are added during this period: only Spain-readiness, packaging and reliability.

10Team and partner role

What we need from you

11Risks

12Open decisions

Questions to settle together over the next few weeks.

1. Final euro pricing for the license, maintenance and customisation work.
2. Should we offer managed hosting from launch, or only installation on the client's own server?
3. Which Spanish regions to target first, and whether Catalan is needed early.
4. Product name: check that "FutureDesk" is free to use as a brand in Spain and the EU.
5. How the partner is paid: commission per license, share of maintenance, or both.
6. Who handles first-line support in Spanish.