Internal Tools and Digital Customer Journeys
Replace one spreadsheet- or email-heavy flow with a focused tool that gives users a clear next step and the business better visibility.
Reply within one business day · No commitment · Fixed price after scope is clear
Pricing
Assessment: fixed price NOK 7,500, credited toward the price if you go ahead with a pilot (NOK 39,000, up to 30 hours).
Further implementation: Priced on request
Who this is for
- Service businesses with manual booking, follow-up, or case handling
- Teams needing one shared workspace instead of multiple spreadsheets and inboxes
- Organizations with a clear process owner and a focused first user need
Signs this may be relevant
- Users must contact the business to understand availability or the next step
- Status and ownership are spread across inboxes, spreadsheets, and verbal updates
- Staff enter the same information in multiple places
Included in the delivery
- User and process map with a prioritized first flow
- Clickable prototype before full implementation
- Responsive, accessible interface for the agreed journey
- Agreed integrations, roles, and administration functions
- Production release, operating notes, and a prioritized improvement backlog
Scope and engagement model
For service businesses that need a practical booking, customer, or internal workflow—and where standard software has either been assessed or does not cover the critical process well enough.
A focused product engagement with a prototype, agreed first version, and handover. Fixed pricing follows the defined journey, roles, integrations, and acceptance criteria.
How the delivery works
Choose the journey
Define the audience, job to be done, ownership, and first-version goal.
Prototype
Test information structure and critical steps before integrations and detail work.
Implement
Build the agreed flow with access control, validation, and required connections.
Launch and learn
Release in a controlled way, document operations, and prioritize the next improvement from real use.
Important boundaries
Standard software is considered before custom development. Ongoing content work, third-party licenses, unknown integrations, and post-handover support are included only when explicitly agreed.
Frequently asked questions
Should we buy standard software instead?
If standard software covers the need with acceptable adaptation and cost, it is often the right choice. Custom development should solve a clear gap.
Can we start with a prototype?
Yes. A clickable prototype of the critical flow reduces specification errors and makes scope and fixed pricing more precise.
What happens after launch?
The delivery includes agreed testing, production release, and operating notes. Further development or support is contracted separately so ownership remains clear.
Which workflow is still held together by inboxes and spreadsheets?
Describe the user, critical steps, and surrounding systems. The first version can then be scoped without building more than necessary.
Contact
+47 909 22 042 · victor.berg@vimplement.com
Response within one business day.