Customer portals
For customers and partners: orders, statuses, documents, payments, history.
Raddev · Development
Web and mobile app development
We build customer portals, internal systems for staff and mobile apps. We start with the work the app should take off people's hands — phone calls, spreadsheets, sending files back and forth — and design around that.
We'll reply within 24 hours, clarify the details and send you possible solutions with an approximate price.
What clients come to us with
Pick your situation — we'll show what we do.
Your situation01 / 06
—
What we do—
Send a request
We'll reply within 24 hours, clarify the details and send you possible solutions with an approximate price.
What we do
Internal systems
For staff: requests, tasks, inventory, schedules, reports. With roles and access rights.
Mobile apps
Ordering, booking, appointments, notifications.
First product versions
For new services: a minimal feature set, launch, improvements based on feedback from the first users.
How we work
- 01
Request and conversation
You describe the task in your own words. Within 24 hours we write back and clarify: who will use the app, which processes it will replace, which systems it must work with.
What you getpossible solutions with an approximate cost for each stage.
- 02
Planning
User scenarios, roles, prototypes of key screens, a data and integration diagram.
What you geta prototype, a feature description and an exact development estimate.
- 03
Design
Design of screens and states: errors, empty lists, loading. The designer agrees the mock-ups with the developers before showing them to you.
What you getmock-ups that can be built within the agreed time and budget.
- 04
Development in parts
We split the work into parts and show each one on a test address. You can change priorities along the way without waiting for the end of the project.
What you getworking parts of the app you can test on your own scenarios.
- 05
Testing and launch
Testers check scenarios, roles and load. We move the app to the production server and migrate the data.
What you geta working app, access details, the code and a description of how it's built.
What every project includes
- 01
Roles and access rights
Everyone sees only their own part.
- 02
Testing
We test scenarios before launch, not after users complain.
- 03
Data backups
Set up from day one.
- 04
Project documentation
How the system is built, where everything lives, how to develop it further.
- 05
The code stays yours
The repository, access and server are registered to you.
How much it costs
Apps vary a lot in scope, so we name the exact price after the design stage.
One rate€45/hour
For all work, including planning.
How we calculate the price
- 01
After our conversation — an approximate cost for each stage. Free of charge.
- 02
After planning — an exact estimate in hours. You approve it before we start.
- 03
New tasks that come up along the way are estimated for time and cost first. You decide.
- Contract
- Payment in stages
- Estimate before we start
- The code and access are yours
What we build with
Laravel
Back end: logic, data, access rights, integrations.
React and Vue
Interfaces for portals and internal systems.
Mobile development
What usually worries people before the start
"We'll spend a year and a fortune, and nobody will use it."
That's why we start with design and a first version with minimal features. We check how people use it, and only then add the rest.
"Do we really need a mobile app?"
Not always. If customers come back rarely, a mobile version of the website or portal is often enough — it's cheaper and easier to maintain. We'll tell you in our conversation what fits your case.
"Halfway through we'll realise we need it differently — and everything will have to be redone."
We show the app in parts, so changes come up early. New tasks are first estimated for time and cost; you decide whether to do them now or in the next version.
"The developers will leave — and nobody will understand the system."
The code and project documentation stay with you. We use widely adopted technologies, so another team can keep developing the system.
"After launch, everything will start breaking."
Before launch, testers check scenarios and roles. The bug-fix warranty is set out in the contract. After launch we can take the app on for support.
"It needs to connect to our accounting system, CRM and payments."
We design integrations at the first stage, together with the data model. More on the Integrations page.
Raddev · Get in touch
Tell us what the app should do.
What happens after you send a request
- RequestDescribe the task in your own words — in the form or in a messenger.
- ConversationWe'll write back within 24 hours and clarify the details.
- Possible solutionsWe'll send you possible solutions and an approximate price. Free of charge.