Recommended Services
Supported Scripts
App Development · Rotterdam
Applications for spreadsheet replacement.
Connect the right tools.
A custom app should make responsibilities and record changes easier to follow. Start with the handover that causes the most friction, including its exceptions. Confirm which existing tools expose the data and actions the application requires.
- Web applications and portals
- Tools for your team and customers
- Connections to your existing systems

PURPOSE BEFORE TECHNOLOGY
A useful first version.
A clearer next decision.
We define the task, the people involved and the information they need before selecting technologies.
Customer portals
Give customers or staff access to the records and actions relevant to their role.
Internal tools
Organise a repeatable internal process with clear responsibilities and visible progress.
Digital products
A focused first release that tests the core service before the product grows.
A FIRST RELEASE WITH A CLEAR PURPOSE
A defined first release.
Not an endless wish list.
We separate essential functionality from later improvements and record the boundaries of the first release.
- Core user journey and user roles
- Features and data for the first release
- Dependencies on third-party services
- Testing and acceptance criteria
THE PROJECT PLAN
Turn requirements
into a working release.
- Goal—what needs to change for the user
- Workflow—how the core task is completed
- Data—what is stored and who can access it
- Release—what is delivered and how it is tested
DEVELOPMENT IN CLEAR STAGES
See what is ready.
Know what comes next.
01
Discovery
The specification records who the application serves and what a successful task looks like.
02
Prototype
We test the core screens and user journey before investing in the complete build.
03
Development
We deliver reviewable increments so feedback can influence the work while it is still in progress.
04
Testing & release
We check the release, organise deployment and clarify ongoing support responsibilities.
Connected applications.
Less duplicated information.
- CRM and customer service tools
- E-commerce and payment services
- Files, databases and reports
- APIs and automated updates
INTEGRATIONS THAT MAKE SENSE
Build connections,
not another data silo.
Integrations are planned around record ownership, access and the direction of each update.
API access and external platform limitations are checked before the integration scope is agreed.
BEYOND THE FIRST RELEASE
Think beyond launch day.
Roles & access
Permissions specify which users may view or change each type of information.
Testing real workflows
Testing includes what happens when a request fails or the user does not follow the expected path.
Handover & maintenance
Your team should understand what has been delivered and how changes will be handled after release.
FREQUENTLY ASKED QUESTIONS
Questions before the first release.
Use filters that help users distinguish the products they need. Start from the catalogue data and representative search tasks, then test whether the controls improve the result.
Agree field mapping, cleanup rules and a verification sample before importing. Keep a way to reconcile the imported data and decide how changes during the transition are handled.
Include the complete path for one useful task, including errors and staff handling. A long list of screens is less useful than a release that users can actually complete a job with.
We first review the code, documentation, dependencies and available access. We can then determine whether it makes sense to continue development, upgrade in stages or build a new solution.
Usually it can be one application with an appropriate language model. The architecture depends on shared data, translation ownership and any genuinely different market rules.
A PRACTICAL STARTING POINT
Build an application that handles language deliberately.
Language can affect interface text, entered data, dates and notifications. Define which parts change and which records remain shared across versions.
01 · Prepare
List the languages, important terms and the person who can review each version. Separate translation from the decision to enter a market.
02 · Verify
Follow the same important journey in each intended language. Check navigation, forms and messages rather than the headline alone.
03 · Keep ownership clear
Assign responsibility for keeping language versions aligned when products, services or policies change.
Illustrative sequence. The actual configuration and responsibilities follow the agreed requirements.
DELIVERY & OWNERSHIP
Keep the first change small enough to verify.
Identify the one outcome that makes the initial work useful. Put later additions in a separate list so the first delivery has a clear boundary.
01 · Prepare
Build one complete user task before extending the application’s feature list.
02 · Verify
Ask a representative user to complete the first agreed task, including a rejected input and a recoverable error.
03 · Keep ownership clear
Define the accepted release, its administrator and the next feature decisions outside the initial scope.
OUR WORK
Applications built around real tasks.
Selected work in bookings, portals and digital products.

Arnos
Education with organised access
We designed an educational website with service categories, study information and e-learning tools, making its content easier to navigate.

Jim’s Group
WordPress, bookings and connected systems
We developed a WordPress booking platform connected to the group’s management system, an Angular application for monitoring requests and a shared foundation for individual division websites.
IN OUR CLIENTS’ WORDS
“They always deliver and are very creative with web design/development. They are absolute masters of WordPress. They have also been great with dealing with a large number of stakeholders within business.”
Joel K. · Jim’s Group
SERVICE AREA
For your audience in Rotterdam.
Products and catalogues.
Serving Rotterdam can involve customers with different usage patterns. Describe when and how the audience uses the service rather than assuming the city name predicts demand.
Check concurrent actions, important limits and the expected user journey.
The map identifies the audience area. Project scope, collaboration and delivery are agreed around the business and its users; it does not imply a local office.
- Users doing the work
- Exceptions and approvals
- Ownership of notifications
Rotterdam
THE NEXT STEP
Tell us what you need
your application to do.
Describe the users, the problem and the outcome the first version must deliver.
YOUR NEXT STEP
Build an application that handles language deliberately.
Share the existing providers and the connection you need. We can check the dependency before promising an implementation.
Confirm which existing tools expose the data and actions the application requires.
