Skip to content
Fenix-Web

Services

Websites, automations and software that take work off your business.

Fenix Web is a software and web studio in Vienna. We build the public presence of businesses in every sector, automate the workflows behind it and develop our own applications where off-the-shelf software misses the business. How solid that is you can see in our own products: GastroFlow and NeoPOS run in live operation.

Three areas, two products of our own

  • Websites for trades, retail, services, healthcare and local businesses.
  • Automations that take recurring manual steps out of the working day.
  • Custom software — customer portals, internal tools, licensing systems.
  • GastroFlow and NeoPOS as in-house products — evidence, not a fourth service area.

Not everything at once: Most businesses start with one area — usually the one that costs the most time today. The rest can be added later without starting over.

  • GDPR-compliant Data stays in your own instance, not in a third-party portal.
  • Hosting in the EU Operations and backups in Austria or Germany.
  • Reply in under 1 business day Support Mon–Fri, 9 am–6 pm from Vienna.
  • Transparent contract Fixed scope, fixed fee, monthly-cancellable support.

Overview

Three service areas. You rarely need all three.

So that you do not have to read the whole page: here is what the three areas do and who they are meant for. Jump straight to the one that fits your business. The fourth route leads to our own products — that is not an offer, but the evidence behind it.

Websites

The public presence: being found, building trust, receiving requests. For businesses whose website is older than what they currently offer.

Go to Websites

Automations

Recurring workflows run without a hand on them: distributing requests, confirming appointments, moving data between systems. For businesses that do the same work more than once.

Go to Automations

Custom software

Customer portals, internal tools and licensing systems, where no suitable product exists for your case. For businesses with a workflow that no off-the-shelf solution covers.

Go to Custom software

Our own products

GastroFlow for hospitality and NeoPOS as the POS system — built by us and run by us. For hospitality businesses a direct route, for everyone else the evidence that we run what we build.

Go to our own products

Not sure which area fits? The free Digital-Check will tell you — without you having to commit to anything first.

Service area 01

A website that brings in requests — not one that just looks good.

Most business websites do not fail on design, but on three things: they are awkward on a phone, they do not say clearly what the business does, and the request lands in an inbox nobody looks into often. That is exactly where we start.

What you end up with

  • A site that works on the phone first — that is where most visitors arrive.
  • A clear structure: what you offer, for whom, and how to reach you. In that order.
  • Content you can change yourself — opening hours, prices, services, without calling the studio.
  • Forms that arrive where someone reads them: inbox, calendar or directly in the workflow behind it.
  • Local findability as a foundation: clean structure, real copy, correct business details.
  • The legal framework taken into account: legal notice, privacy notice and consents are part of the scope.
  • Accessibility as a benchmark — WCAG as a guide, without claiming an audit badge.
  • Domain, hosting and access credentials run on your own accounts. You remain free to switch at any time.

The same work looks different in every sector. Six typical starting points:

Starting point

The jobs come in by referral, the website is from 2016 and shows services that no longer exist in that form. Requests come in by phone — usually when nobody is there to answer it.

What gets built

A lean site with services, coverage area and reference photos from your own projects. A request form with photo upload, so the customer can show straight away what it is about.

What changes day to day

Requests arrive in writing and complete, instead of as a call-back request on voicemail. Preparing a quote starts with information instead of a phone call.

Typische Anwendungsfälle — keine Kundenreferenzen. Echte Projekte zeigt Fenix Web erst nach schriftlicher Freigabe des Betriebs.

Service area 02

The work nobody wants to see: set it up once, then it runs.

In almost every business there are tasks that run the same way every week: typing data from one system into the next, writing confirmations, pulling lists together. That is not work you hire staff for — it is work that eats staff. Automation takes it out of the day.

For whom

Businesses with several areas of responsibility, where every request first lands in a shared inbox.

What happens today

Someone reads the inbox, decides who is responsible and forwards it. During holidays or sick leave the request sits there.

How the automation works

The form records the type and subject of the request. The automation files it in the right inbox or system, notifies the person responsible and sets a deadline.

How you notice it

No request goes unanswered for two days because nobody assigned it.

For whom

Businesses that record order data twice today — once in email, once in the invoicing program.

What happens today

The same data travels by copy-and-paste between email, spreadsheet and accounting. Every step is a source of errors.

How the automation works

The order data is recorded once and handed to the existing invoicing or accounting system. Follow-up documents come from the same record.

How you notice it

The invoice run becomes a review step instead of a typing job.

For whom

Businesses that work by appointment — workshop, practice, consulting, services.

What happens today

Appointments are agreed by phone, written into the calendar by hand and never followed by a reminder. A no-show costs a whole slot.

How the automation works

The appointment is created online or by phone, the confirmation goes out automatically, and so does the reminder. Cancellations release the slot again.

How you notice it

Fewer forgotten appointments and fewer phone calls that serve only to confirm.

For whom

Businesses that run website, inventory management, till and accounting side by side.

What happens today

Each system holds its own version of the data. Which one is right only becomes clear when something goes wrong.

How the automation works

Through the systems’ existing APIs — or through one of our own where none exists — the data is kept authoritative in one direction. One source, the others follow.

How you notice it

Nobody has to compare which version is the right one any more.

For whom

Businesses that maintain services, prices or opening hours in several places at once.

What happens today

The change happens on the website, but not on the printed notice, in the business directory or in the quote letter.

How the automation works

The data lives in one place and is published from there to the other channels.

How you notice it

No customer stands in front of a locked door because of outdated opening hours.

For whom

Managers who currently assemble monthly figures from several exports.

What happens today

At the start of the month, lists are exported, copied into a spreadsheet and added up by hand.

How the automation works

The report is produced automatically from the existing data and is in the inbox at the agreed time — as figures, not as a collection of charts.

How you notice it

The figures are there before anyone asks for them.

Do the maths yourself: Take one of these workflows, count how often it occurs per week and multiply by the minutes it costs. That figure times 50 weeks is the effort in question. We deliberately quote no percentages from other people’s studies — your own calculation carries more weight.

Service area 03

When off-the-shelf software misses the business.

Off-the-shelf products cover eighty percent. The remaining twenty are usually exactly what makes the business what it is. For those twenty percent we build our own applications — not for their own sake, but when adapting an off-the-shelf solution works out more expensive than building one.

Customer portals

A protected area where your customers can look up for themselves what they would otherwise ask for by phone: status, documents, contracts, appointments.

  • Sign-in with roles and permissions
  • Documents and status instead of follow-up questions
  • Data stays in your own instance

Internal tools

Applications for your own team: planning, data capture, approvals. Built along your workflow, not along a product catalog.

  • Only the functions the workflow needs
  • Usable without a week of training
  • Grows with you when the workflow changes

Licensing and delivery systems

If you ship software or modules yourself: signed licenses, binding to the respective instance, runtimes and module scope recorded verifiably.

  • Ed25519-signed licenses
  • Domain binding with runtime and module scope
  • Offline grace so that operations do not come to a halt

Licensing technology in detail

APIs and integrations

The connection between your systems — using existing APIs, building the ones that are missing. Documented, so that others can carry on working with it.

  • REST APIs, documented instead of handed over verbally
  • Connection to existing systems
  • Traceable error handling instead of silent failures

When we advise against it: If an off-the-shelf solution covers ninety percent of your case, building your own is the more expensive answer. We say so in the first conversation — even when it means a project falls away.

Our own products

We do not only build for others. We run two products of our own.

GastroFlow is our own platform for hospitality: digital menu, QR table ordering, kitchen ticket, reservations, guest data, analytics and integrations. On top of that comes NeoPOS as our own POS system. Both run during evening service, where half a minute of delay is noticed immediately. That is why they are here — not as an offer to every business, but as evidence of how we build.

  • Our own products means we bear the consequences of our technical decisions ourselves — including support, updates and outages.
  • The licensing system, the REST API and the update path are proven on a real product, not on a prototype.
  • The product area also includes NeoPOS, our own POS system. For cash registers in Austria, RKSV applies — that is the legal frame, not a quality seal and not German TSE.

GastroFlow — the studio's hospitality platform

Menu, QR ordering, kitchen and reservations in one install. Prices, features and trial are on the product pages.

Direct: Features Pricing Process

Not a hospitality business? Then GastroFlow is just information for you: this is what software we run ourselves looks like. Your project falls into one of the three areas above.

Technology

A modern stack — the point is not the technology, but what it saves you.

Technology names sell nobody anything. What matters is what they mean day to day: how quickly you go live, what running it costs per month, and whether the solution will still hold up in three years.

Live sooner

We rely on proven building blocks instead of reinventing things for every project. A clearly scoped project is therefore ready to launch in weeks, not quarters.

Technically behind it: our own module catalog, reusable components, a shared design token system.

Cheaper to run

No chain of licenses for third-party subscription tools that gets more expensive every year. What costs money on an ongoing basis is fixed in advance — and can be cancelled.

Technically behind it: your own instance, hosting in the EU, no platform fee per transaction.

Future-proof

Your data sits in your own instance. A change — of provider, of hosting, of direction — is possible at any time, without anything being left behind.

Technically behind it: documented neoweb/v1 REST API, open data structure, access credentials on your own accounts.

Ahead of the website builder

Website builders are quicker at the start and in the way from the first special case onwards. We carry on building where the builder stops: on your workflows.

Technically behind it: custom extensions, custom data models, automations instead of click limits.

Stack at a glance

Website base your own instance
PHP 8.0 or higher
REST API neoweb/v1
Signing Ed25519
Binding Domain, runtime, module scope
Offline Grace period, operations keep running
Accessibility WCAG as a benchmark

Licensing and delivery technology in detail

Objections first

Benefits issues

If your question is missing: write briefly, we will answer within a business day.

No. We build websites, automations and custom software for businesses in every sector — trades, retail, services, healthcare, local businesses. GastroFlow is our own product for hospitality and therefore a special case, not the studio’s focus.

No, but it helps to start with one. In practice it usually begins with the website, and the first automation grows out of what we notice while building it.

Not necessarily. Sometimes it is enough to sort out the requests behind it and connect two systems. The free Digital-Check tells you whether a rebuild pays off at all.

An automation connects and speeds up what is already there. Custom software is built where no system exists for your workflow at all.

No. Domain, hosting, access credentials and data run on your own accounts, and the APIs are documented. Ongoing care is a separate line item, cancellable monthly — not a precondition for the solution to work.

Yes. You change texts, images, opening hours, services and prices yourself. We hand over with a short briefing, not a week of training.

Next step

Which field brings you the most?

Describe in two sentences what costs time today. You get an assessment of which step pays off – and which one you can save yourself.

free and non-binding no newsletter reply within one business day

Action completed