Sales with a next step
Contacts, communication history and open opportunities. The sales module is in development.
Our products for sales and operations
We develop our own tools around specific business workflows. Choose the direction that fits your work, from proposals and invoices to machine configuration and service.
Discuss deploymentRelviyo
From first contact to paid invoice
We are developing sales, proposals and a client workspace in one system. For smaller teams that want a clear picture even after the deal is agreed.
Request a Relviyo walkthrough
Proposals and invoicing
The existing prototype supports templates, PDF, proposal-to-invoice item transfer and payment records.
A shared client workspace
Documents, materials, messages and approval of a specific proposal version through a project link.
Keep the relationship moving after approval
Who follows up with the client
A contact on a phone, a proposal in email and the next step in someone’s head.
Goal: history and the next step alongside each clientWhich proposal is the latest
Multiple attachments, revised prices and unclear approval.
Document versions and approval in the client workspaceWhy enter the same data again
Agreed items are manually copied into an invoice.
Proposal-to-invoice item transfer in the prototype04steps in one workflow
Enquiry
Proposal
Approval
Invoice
The proposal is agreed The work continues
Clients need to provide materials, confirm the scope and find the correct invoice. Teams need to know who acts next and what remains pending. Relviyo is being designed to connect these steps.
Request a Relviyo walkthrougheInvoicing within Relviyo
From an agreed proposal to invoicing and delivery. A Peppol connection is planned as a Relviyo extension; the current document prototype uses PDF and exports.
Discuss invoicing in RelviyoStart with one sales workflow
We will show the existing document prototype and review your enquiry-to-invoice workflow. We will propose a pilot scope, integrations and pricing approach.
Request a Relviyo walkthroughThrive Machines
Your machine in context from design to service
We are developing a digital workspace for manufacturers and service teams. Existing prototypes demonstrate equipment configuration, part selection and access to documentation.
Discuss a pilot for my machine
One machine, three perspectives
Design needs the assembly. Service needs the specific part. Operators need the right guide. Each role can access the information it needs.
3D configuration
Dimensions, materials and modules. Configuration and space checks, indicative pricing and a component list.
Parts and service
Select parts on the model, explode the assembly and access related guides. Prepare a part or service request.
Documentation via QR
Machine identification and documents. Deployment adds manufacturer content, versions, languages and long-term availability.
When the machine stops, the search must end
Which part do we actually need
A photo without an identifier triggers another round of questions.
Select the component directly in the 3D modelWhere is this machine’s manual
A technician searches through folders and old messages.
Documents attached to the specific equipmentCan this configuration be assembled
Dimensions and combinations are checked after an enquiry.
Configuration checks and an indicative component list
Find the right part without a lengthy search
A technician opens a specific machine, selects a component in 3D and finds its identifier and guide. A part request starts with a clear identification and the relevant context.
Discuss a pilot for my machineProduct data has its place too
A digital product passport is a possible planned extension: materials, suppliers and documentation according to the requirements of the specific product category.
Your machine as the first demonstration
We will review your available CAD model, part list and documentation. We will propose a pilot for one equipment type and prioritise configuration or service around your needs.
Discuss a pilot for my machineShow us where work gets stuck
We will review your workflow, show the existing foundation and agree on a pilot scope.
Discuss deployment