[01] admin
Internal admin and back-office systems
- orders, clients, content and workflows in one place
- role-based permissions
- Filament-based admin, up to a full multi-tenant SaaS product
$ build --custom admin · portal · app
Custom software
development
We build custom software where off-the-shelf tools no longer fit how you work: internal admin and back-office systems, client portals, web apps and mobile apps, connected to the tools you already use. FlowProject is an independent digital studio in Budapest, working since 2019; a core team of three and eight trusted partners design and build on Laravel, Livewire and Filament.
// when_it_pays_off
When does custom software beat an off-the-shelf tool?
If an existing product covers what you do well, we'll recommend it, because it's faster and cheaper to start with. Custom development is a good investment when your process is your competitive edge, or when manual work costs more over time than building and running a system.
We wrote up the same trade-off for adopting AI: where it actually pays off, and where it doesn't →
Signs you've outgrown the off-the-shelf option:
- your team types the same data into several places by hand
- spreadsheets hold the business together, and only one person understands them
- you work around the software instead of it fitting your process
- you use several tools that don't talk to each other
- clients email you for things they could sort out themselves in a portal
// what_we_build
What we build
[02] portal
Client portal
- an account where your clients can see and handle things
- statuses, documents and orders in one place
- a shared login with your webshop or app
[03] web app
Web app and PWA
- runs in the browser, no app store download needed
- installable to the phone's home screen
- designed for mobile, with large touch targets
[04] mobile
Mobile app
- React Native and Expo, iOS and Android at once
- push notifications, API connection to your own system
- App Store and Play Store publishing included
[05] integration
Integrations
- Billingo, Számlázz.hu, Stripe, SimplePay
- Google APIs, Mailchimp, HubSpot
- custom APIs, webhooks, background queues
[06] automation
Automation
- automated invoicing and admin work
- an internal dashboard for the numbers you now collect by hand
- if you do something by hand on a regular basis, we turn it into a system
If a shop is a central part of your system, see our webshop development page. If the automation is about your marketing, our AI marketing team handles it.
// stack
What we build with
No framework wars. What matters is that the system is fast, accessible and still works three years from now, even if a new developer joins along the way.
So we typically build on Laravel, use Livewire or React for interfaces, Filament for the admin and React Native for mobile. Hosting is chosen to fit the project (Hetzner or DigitalOcean, with Cloudflare in front); if the data has to stay in Hungary, in a Hungarian data centre, as with G8.
- Backend: Laravel, PostgreSQL, Redis for queues and cache
- Frontend: Livewire or React, Tailwind CSS
- Admin: Filament
- Mobile: React Native, Expo
- Payments: Stripe, SimplePay
- Infrastructure: Hetzner, DigitalOcean, Cloudflare CDN and R2
// process
Six steps we don't skip
We go through the same six steps on every software project. You get one day-to-day contact who stays with you from the first email, and when you ask something, a real person answers.
Maintenance: for three months after launch we watch real usage and adjust, because planned and actual usage are never the same. Updates, security fixes and new features are agreed separately after that.
Whoever you work with, settle one thing in writing at the start: who will own the source code, and who has access to the server, the domain and third-party accounts. Feel free to ask about it when you request a proposal.
- 01Ask
A workshop, interviews, existing material. At the end, everyone has the same picture in mind.
- 02Listen
User interviews. The client knows what they say; the user knows what they do.
- 03Sketch
On paper. What's wrong on paper will be wrong in Figma too, you just find out later.
- 04Build
Two-week sprints, a weekly demo, a weekly decision. No weeks of silence.
- 05Ship
Staging first, production after approval, rolled out gradually. Nobody gets surprised.
- 06Measure
Three more months after launch: we see how it's really used, and adjust.
// reference
Reference: G8 Alakváltók
Géza Goócz's ten-week lifestyle programme (client: BIOHACK Kft.) used to run on several separate systems, each with its own login and its own data. We built the participant app, the webshop and the website as one Laravel system, with shared accounts and a shared admin.
- One codebase, one database. Laravel and Livewire for the interfaces, Filament for the admin. A purchase automatically grants access to the right programme.
- Participant app. A mobile-first web app, installable to the home screen: daily diary, weekly measurements, progress tracking, lessons and videos unlocking on schedule.
- Hosting in Hungary. The data lives in a Hungarian data centre, which matters for a health-related programme.
- Staged releases. Every change went to a test environment first and to production only after approval, even with a cohort running.
Today the team sees orders, participants and content in one admin, and sets up new cohorts and products without a developer.
Is there a process you currently hold together with spreadsheets and manual work? Describe it in a few sentences. After a free consultation we'll send you a tailored proposal.
$ let's_talk() →// faq
Frequently asked questions
How much does custom software development cost?
We don't publish prices, because the cost of custom software depends on the scope, the integrations and the number of users. After a free consultation we send a tailored proposal written for your processes.
When is off-the-shelf software better than custom?
When an existing product covers what you do well and doesn't need to be bent around your process. In that case we'll say so rather than build something you don't need. Custom software pays off when your process is your competitive edge, or when manual work costs more over time than building and running a system.
What technology do you use?
Typically Laravel, Livewire or React, a Filament admin, PostgreSQL and Redis; React Native and Expo for mobile. Hosting is on Hetzner or DigitalOcean, with Cloudflare in front.
Can you connect to our existing systems?
Yes, integration is a big part of what we do: Billingo, Számlázz.hu, Stripe, SimplePay, Google APIs, Mailchimp, HubSpot, plus custom APIs and webhooks between any two systems.
Do you build mobile apps too?
Yes, with React Native and Expo, for iOS and Android at once, including app store publishing. Often a web app installable to the home screen (PWA) is enough; we decide that together during planning.
What happens after launch?
For three months after launch we watch how the system is actually used and adjust it. Maintenance, updates and further development are agreed separately after that.