Websites
The public presence: being found, building trust, receiving requests. For businesses whose website is older than what they currently offer.
Services
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
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.
Overview
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.
The public presence: being found, building trust, receiving requests. For businesses whose website is older than what they currently offer.
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.
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.
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.
Not sure which area fits? The free Digital-Check will tell you — without you having to commit to anything first.
Service area 01
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.
The same work looks different in every sector. Six typical starting points:
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.
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.
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.
The shop lives off its location, but online all you find is a map pin and a phone number. Range, opening hours and promotions are nowhere to be found reliably.
A site with the main product ranges, current opening hours, directions and promotional areas you fill yourself. Connected to your existing inventory management system on request.
People searching locally find current information instead of an outdated page. You change opening hours yourself, in a minute.
The offer needs explaining, but the website does not explain it. Prospects ask the same three things by email over and over.
A site that sets out the service, the process and the price range in an understandable way, with an FAQ for the questions that always come up and an appointment route instead of a long form.
First conversations start better informed. The follow-up questions that used to cost time are answered by the site.
Patients first look for opening hours, directions and the range of treatments — and find a page that is unreadable without zooming in.
A calm, easily readable site with the range of treatments, hours, stand-in arrangements and directions. Forms that collect as little data as possible and state clearly what happens to the details.
Fewer calls about organisational questions, more time for what the practice is there for. Data protection is part of the construction, not a text in the footer.
The business has grown, the website has not. Several locations, several contacts, but only one general contact address.
A structure that grows with the business: locations, teams and services as their own areas, requests routed automatically to the right place.
Requests land directly with the right person. You add new locations or services without the site having to be rebuilt.
The menu lives as a PDF or Instagram post, opening hours are often outdated, reservations run via phone and messenger. Guests search online and find no current menu.
A website with an editable menu, opening hours, directions and a QR menu in the browser — no app download. Optionally connected to GastroFlow.
The menu is up to date online. Guests scan the QR code and read the menu in the browser. Reservation requests land where someone actually reads them.
Typische Anwendungsfälle — keine Kundenreferenzen. Echte Projekte zeigt Fenix Web erst nach schriftlicher Freigabe des Betriebs.
Service area 02
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.
Businesses with several areas of responsibility, where every request first lands in a shared inbox.
Someone reads the inbox, decides who is responsible and forwards it. During holidays or sick leave the request sits there.
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.
No request goes unanswered for two days because nobody assigned it.
Businesses that record order data twice today — once in email, once in the invoicing program.
The same data travels by copy-and-paste between email, spreadsheet and accounting. Every step is a source of errors.
The order data is recorded once and handed to the existing invoicing or accounting system. Follow-up documents come from the same record.
The invoice run becomes a review step instead of a typing job.
Businesses that work by appointment — workshop, practice, consulting, services.
Appointments are agreed by phone, written into the calendar by hand and never followed by a reminder. A no-show costs a whole slot.
The appointment is created online or by phone, the confirmation goes out automatically, and so does the reminder. Cancellations release the slot again.
Fewer forgotten appointments and fewer phone calls that serve only to confirm.
Businesses that run website, inventory management, till and accounting side by side.
Each system holds its own version of the data. Which one is right only becomes clear when something goes wrong.
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.
Nobody has to compare which version is the right one any more.
Businesses that maintain services, prices or opening hours in several places at once.
The change happens on the website, but not on the printed notice, in the business directory or in the quote letter.
The data lives in one place and is published from there to the other channels.
No customer stands in front of a locked door because of outdated opening hours.
Managers who currently assemble monthly figures from several exports.
At the start of the month, lists are exported, copied into a spreadsheet and added up by hand.
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.
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
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.
A protected area where your customers can look up for themselves what they would otherwise ask for by phone: status, documents, contracts, appointments.
Applications for your own team: planning, data capture, approvals. Built along your workflow, not along a product catalog.
If you ship software or modules yourself: signed licenses, binding to the respective instance, runtimes and module scope recorded verifiably.
The connection between your systems — using existing APIs, building the ones that are missing. Documented, so that others can carry on working with it.
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
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.
Menu, QR ordering, kitchen and reservations in one install. Prices, features and trial are on the product pages.
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
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.
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.
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.
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.
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
Objections first
If your question is missing: write briefly, we will answer within a business day.
Next step
Describe in two sentences what costs time today. You get an assessment of which step pays off – and which one you can save yourself.