Placeholder photoLiveUnder NDAcorporate catering and lunch delivery
Corporate catering
A corporate lunch platform: staff order a week ahead, the company sets the limit, the kitchen gets ready-made labels and sheets.
Service
Customer accounts and portals
We build web portals with accounts for different roles: customers order and see statuses, companies set rules and limits, suppliers manage their catalogue. One system, and everyone sees only their own part.
Animation: a shared system sends data to three separate role accounts in turn, and each one shows only its own rows.
When you need it
Situations that bring people to us for this service.
Everything goes through a manager
Customers can't order, change or check a status themselves — only by email or phone.
Several parties in one process
Customer, company and supplier swap spreadsheets, and someone merges them by hand.
Rules rest on agreements
Limits, who pays and until when an order can be changed are written down nowhere.
Too much access
A shared spreadsheet shows everyone everything, although each needs only their own part.
What's included
Role analysis
Who uses the portal, what each sees and changes, where responsibility passes on.
Role accounts
Separate accounts — for example, for employees, companies and suppliers — in one system.
Orders and requests
Orders placed in advance with a cut-off after which they can't be changed; requests with statuses, documents and correspondence.
Company rules
Branches, offices, employees, a daily spending limit and who pays — in the company account.
Supplier account
Categories, items, main and extra menus, hidden items, photos.
Online payment
A payment service and a check that the payment really went through.
Documents and mailings
Spreadsheets, PDFs and labels on a schedule — emailed to those who need them.
What you get
- A description of roles and permissions
- A prototype of the portal's key scenario
- A portal with an account for each role
- Online payment, if you need it
- Code and documentation that are open to you
The project path
From the first conversation to daily use
Every step ends with a decision: go on or stop. We don't start the next one until the previous one has given its answer.
- 01
Getting to know the task
You describe the process and what gets in the way. We reply by email with questions and arrange a call.
- 02
Discovery
We study the process with the people who work in it and write down what the system must change and how we will check it.
- 03
Prototype
We build a working prototype of the key scenario to test the idea on real data rather than on polished screens.
- 04
Pilot
We run the system in your real environment with agreed outcome criteria and a deadline. After the pilot we decide together whether to go further.
- 05
Launch and growth
We bring it to daily use: reliability, access rights, links to other software, documentation, support. Then we develop it based on user feedback.
Related case studies
Systems where we have already done this kind of work.
- Placeholder photo
Placeholder photoLiveUnder NDAroad freight transport in EuropeFreight management
Rate quoting and transport request management for a European road carrier, its partners and end customers.
Technology in these case studies
- Strapi
- PostgreSQL
- Next.js
- LiqPay
- Puppeteer
- REST API
- JWT
- Excel
Questions about this service
How many roles can a portal have?
As many as your process has. In the corporate catering case study there are four: employee, company, caterer and system administrator.
Can payment be connected?
Yes. In the corporate catering case study employees pay through LiqPay, and the system checks that the payment really went through.
Will the portal connect to our system?
Yes — exchanging data with what already works is one of our principles. What to pass across we decide during discovery.
More in “Websites”
- Corporate website developmentA website that makes clear what your company does and takes enquiries, with content your team updates without a developer.
- Online storesA catalogue, a cart, online payment and orders that don't get lost between the website, the warehouse and delivery.
- Landing pages and product pagesOne page for one product or offer: who it's for, what's inside and how to get in touch — clearly.
- Service websites with a price calculatorCustomers learn the price before they call, and the enquiry with its calculation is stored in the system with a status.
- Partner websites under the partner's brandOne system, many sites: partners sell your service under their own brand, language and prices.
- Multilingual websitesOne site in several languages — with correct tags for search and separate copy for different markets.
Have a project with no ready-made solution?
Describe it in a few sentences: how things work today and what gets in the way. We reply by email with questions on the next business day.
Get in touch