CRM, proposals and contracts connected to the laboratory
Organize opportunities, proposals and contracts with data connected to the laboratory workflow. Enabling the opportunities CRM depends on the contracted plan.
Illustrative system screen. Demo data that does not represent client results.
From opportunity to work order
The data from one step is reused in the next, which helps reduce re-keying between sales and the laboratory. In the demo, you see an approved proposal become a contract and a work order.
- 1
Opportunity
The interested contact enters the pipeline through the team's entry or through a form linked to the leads webhook.
Data reused
- Client and contacts
- Source and owner
- Estimated value
- 2
Proposal
The proposal is built from the laboratory's service catalog and linked to the opportunity.
Data reused
- Client and contacts from the opportunity
- Services, parameters and matrices from the catalog
- Prices and payment terms
- 3
Contract and acceptance
The acceptance is recorded with who approved it and when, and the contract is created from the approved proposal.
Data reused
- Services, parameters and prices from the proposal
- Sampling plan
- Term and deadlines
- 4
Work order
Work orders use the contract data and follow the configured sampling plan.
Data reused
- Client and contracted services
- Parameters to analyze
- Sampling dates and prices for billing
Work order creation depends on the sampling plan and the contract setup. Integrations with other systems require configuration.
Sales module routines
See each part of the module in detail. Each feature's availability follows the contracted plan and the permissions of each user group.
CRM and sales pipeline
Each opportunity is a card on the stage board. The pipeline shows the value at each stage, pending tasks and stalled opportunities, without relying on tracking spreadsheets.
See detailsLead capture and automation
Contact requests coming from the website or other tools can enter the pipeline by webhook, at the stage and with the source and owner set in the configuration. Workflows handle the next tasks and the configured emails.
See detailsProposals for laboratory services
The proposal is built from the laboratory's catalog, with services, parameters, matrices and prices. Each change can become a new version, and the client views and approves the proposal through a secure link.
See detailsFrom acceptance to contract and work orders
When the proposal is approved, the acceptance is recorded with who approved it and when. The contract is created from the proposal, with services, parameters, prices and sampling plan, and the sampling plan creates the work orders according to the configured calendar.
See detailsClients, requesters and client portal
In the laboratory, a client usually involves more than one person: the company that contracts and whoever requests the analysis. The records keep these roles apart, and the client portal lets clients check proposals and download reports according to the access granted by the laboratory.
See detailsAutomations and proposal follow-up
Automations are configurable and depend on what the laboratory builds in each flow. Automatic sends only happen when a rule has been configured.
Stage-based workflows
The laboratory builds flows with tasks, waits, decisions and automatic actions, such as emailing the client, notifying a user in the system, adding a note and changing the opportunity stage.
Open and click tracking
Emails sent by the flows can record opens and link clicks, and the flow can take different paths based on the response. Proposal views through the portal link are also recorded, with first and last view and total visits.
Limit of open tracking
An email open is only recorded when the client's email program loads images. So it serves as an indication, not as a read confirmation.
Calls, meetings and WhatsApp conversations can be recorded as an interaction or task on the opportunity. The CRM does not send WhatsApp messages automatically.
Clients should be informed about open tracking under the laboratory's privacy policy.
| Topic | Status | What exists today | Limit / laboratory responsibility |
|---|---|---|---|
| CRM and sales pipeline | Available | Opportunity pipeline with stages, sources, loss reasons, tasks, automations, leads received by webhook, analytics and sync with proposals. Sales module available according to plan. | Access depends on the contracted plan and on the permissions set for each user group. |
| Review of requests and proposals | Available | Proposals have a review field and status, an approval workflow and a record of the decision rule agreed with the client. | Assessing technical capability and resources to meet each request is done by the laboratory. |
| Client portal | Available | Clients download reports as PDF, ZIP, XLSX or CSV, open support requests, and view and approve proposals through the link they receive. | Each client's access is granted and maintained by the laboratory. What is made available, and when, follows the laboratory's setup. |
| API and webhooks | Available | API with signed credentials and access scopes, plus webhooks for events such as work order created, sample received, result approved, report signed or released and client created, with queueing, logging and retries on failure. | Technical documentation is inside the system, available by permission, not on a public portal. Development on the external system's side is up to whoever builds the integration. |
Current features and limits of the sales module
CRM and sales pipeline
- What exists today
- Opportunity pipeline with stages, sources, loss reasons, tasks, automations, leads received by webhook, analytics and sync with proposals. Sales module available according to plan.
- Limit / laboratory responsibility
- Access depends on the contracted plan and on the permissions set for each user group.
Review of requests and proposals
- What exists today
- Proposals have a review field and status, an approval workflow and a record of the decision rule agreed with the client.
- Limit / laboratory responsibility
- Assessing technical capability and resources to meet each request is done by the laboratory.
Client portal
- What exists today
- Clients download reports as PDF, ZIP, XLSX or CSV, open support requests, and view and approve proposals through the link they receive.
- Limit / laboratory responsibility
- Each client's access is granted and maintained by the laboratory. What is made available, and when, follows the laboratory's setup.
API and webhooks
- What exists today
- API with signed credentials and access scopes, plus webhooks for events such as work order created, sample received, result approved, report signed or released and client created, with queueing, logging and retries on failure.
- Limit / laboratory responsibility
- Technical documentation is inside the system, available by permission, not on a public portal. Development on the external system's side is up to whoever builds the integration.
Frequently asked questions
Is the CRM included in the system?
Sales module available according to plan. The opportunities CRM is enabled according to the contracted plan and the permissions of each user group. In the demo, we show what applies to your scenario.
Can I tell when the client opened the proposal?
The system records views of the proposal through the portal link and the opening of the delivery email, when the client's email program loads images. It is an indication for sales follow-up, not a read confirmation. Clients should be informed about this tracking under the laboratory's privacy policy.
Does an approved proposal become a contract?
Yes. The contract is created from the approved proposal, with services, parameters, prices and sampling plan. The acceptance is recorded with who approved it and when.
Does the client need a system login to see the proposal?
No. They access the proposal through a secure link, without entering the laboratory's internal system, and can approve it there.
Does the CRM connect to sampling and reports?
Yes. The client, the proposal and the contract are the same ones used in the work order, sampling and report.
Can I integrate with other systems?
Yes, with configuration. Leads can enter the pipeline by webhook, and events such as proposal created, approved or rejected can be sent to other systems by webhook. Development on the other system's side is up to whoever builds the integration.
See the path from proposal to work order
In the demo, we show a proposal built with catalog services, approved by the client and turned into a contract and a work order, using services similar to yours.