Bond, our sales pipeline, counts a lead
once sales accepts it.
Bond is the sales pipeline our team works in when we find leads for your sales team. Every lead has a status, a source and an owner. Every deal sits in a stage with a value. Overdue follow-ups show up on their own. What each lead became goes back to Prism, without the customer's name.
Where we run your pipeline · Results go to Prism · Customer details stay in Bond
Brands our teams have delivered for
Bond is the CRM where we run a client's pipeline and record what each lead became. PixelCrayons uses it when we find leads for a sales team. Each lead is judged by whether sales accepted it. Won, lost and kept customers are reported back to Prism. Names, emails and deal values are not. It's never sold on its own.
A CRM should show missing evidence
as missing.
No data doesn't mean zero
Missing evidence is shown as missing. It is never turned into a score that looks complete because the field had to hold something.
Every item shows its reason
Each record in the attention list says why it's there. The follow-up is overdue, the account has gone quiet, or the salesperson is behind pace.
Only the salesperson can accept a lead
Marketing can call a lead qualified. But only the salesperson who takes it can make it count. A rejected lead is kept with its reason, so marketing learns from it.
How a lead moves
from first contact to customer.
A lead only counts as accepted once the salesperson agrees to work it. A rejected lead goes back with a clear reason, so marketing learns what a bad lead looks like.
- 01
Capture
Source and campaign recorded as the lead comes in, from a form, an ad or a referral.
- 02
MQL
Marketing-qualified: it met the marketing definition.
- 03
Accept
The salesperson agrees, or returns it with a reason.
- 04
SAL
Sales-accepted and counted. This is the number Prism uses.
- 05
SQL
A qualified opportunity, moving through stages with its age tracked.
- 06
Deal
A value, a stage, a close date and the linked contacts and tasks.
- 07
Customer
Won, and with permission, proof.
MQL: marketing-qualified lead, one that met the marketing definition. SAL: sales-accepted lead, one the salesperson agreed to work. SQL: sales-qualified lead, an opportunity moving through stages.
The screens our team works in,
captured from a test workspace.
Every name and number below is sample data from a sandbox (test) workspace. Your pipeline has the same screens with your leads, your team and your stages in them.
- 01Bond · Leads
Leads: every lead your team is working
One screen lists every lead with its status. The statuses run from new through contacted, qualified, RFP, converted and nurture, plus not a fit. Each row shows the company, where the lead came from, its estimated value, its owner and when it last changed. Filters sit on the same line: mine, my team, inbound, outbound and unassigned. The status labels at the top also count the leads, so you see the whole funnel before you open anything.
Status, source and owner on every lead, sortable and searchable, so nothing sits in a spreadsheet nobody opens.
Sample data from a demo workspace, not a client's numbers - 02Bond · Lead record
Lead record: everything about one lead
Open a lead and everything sits in one panel: contact details, status, source, owner, activity timeline and next steps. Every call, email and note is on the timeline in order. Nothing is scattered across tabs. When the lead is accepted or returned, that decision and its reason stay on the record.
One panel per lead, with the full history and the next step, so a hand-off never loses context.
Sample data from a demo workspace, not a client's numbers - 03Bond · Deals
Deals: the pipeline as a board
Deals sit in columns by stage, with the running total at the top of each. You drag cards between stages. Each deal record holds its value, stage, close date and the linked contacts and tasks. So the board isn't a picture of the pipeline; it is the pipeline. Reports read from the same records.
The whole pipeline at a glance, and every column total adds up from real deal records.
Sample data from a demo workspace, not a client's numbers - 04Bond · Needs attention
Needs attention: what is slipping
Bond lists overdue follow-ups and accounts that have gone quiet on its own. Each shows its owner and how long it has been waiting. Nobody has to remember to check. The dashboard's 'first move' card, shown at the top of this page, does the same for people. It names the salesperson furthest behind pace and says by how much.
The queue explains itself: each item says why it is there and who should act.
Sample data from a demo workspace, not a client's numbers - 05Bond · Signals
Signals: buying signals, with their evidence
Bond watches for events that often come before a purchase. One example is an engineering job left open longer than usual for that type of company. Bond then adds the company to a list with a score. Each signal shows its evidence, with the source and date, and a suggested pitch. The salesperson works down the list and picks one of four outcomes. They can turn it into a lead they own, or keep in touch and check again later. They can also drop it with a reason, or pass it to another Vinove brand. Nothing becomes a lead until a person decides it should.
Each signal names its evidence, so a salesperson sees why it fired before deciding what to do.
Sample data from a demo workspace, not a client's numbers - 06Bond · Response audit
Response audit: how fast, and how well, we reply
This report checks each salesperson's real email against the CRM record. It shows how long the first contact took and how many replies from prospects were answered within 48 hours. It also shows the longest silence and any lead with no note. Every new lead gets a fit score, and every reply a quality score. Each score has a one-line reason taken from the email itself. The needs-attention list names the lead, the owner and the problem, such as a reply with no answer. We hold ourselves to this report on your pipeline.
Response speed and reply quality are measured from the actual email, per person and per region, not self-reported.
Sample data from a demo workspace, not a client's numbers - 07Bond · Reports
Reports: funnel, pipeline and targets
Funnel, pipeline and revenue reports are built in and read from the live records. The funnel-and-targets report puts each stage's count against its target, by channel and by owner. Every number opens the records behind it, so you never have to take a figure on trust.
Every number in a report opens the records it was counted from.
Sample data from a demo workspace, not a client's numbers - 08Bond · Reviews
Reviews: coaching based on the numbers
Each salesperson rates their own week, and the manager signs it off. The result is kept as a running red, amber and green history. The review is based on the numbers in the pipeline. So the talk starts from what happened, not from memory.
Self-rating, sign-off and a history for each person, so everyone can see who is on track.
Sample data from a demo workspace, not a client's numbers
Deal record: value, stage, close date, linked contacts and tasks in one panel.
Bond · Deal record · Sample data from a demo workspace, not a client's numbers
Accounts: every company sold to or served, with industry, size and owner.
Bond · Accounts · Sample data from a demo workspace, not a client's numbers
Contacts: every person tied to an account or a deal, searchable and filterable.
Bond · Contacts · Sample data from a demo workspace, not a client's numbers
What Bond does
for your sales team.
Stages and ownership
You set your own stages and lead sources. Bond keeps how long each deal spent in a stage and who owned it, not only where it sits now.
Targets and pace
Targets for each person and the team. The dashboard shows each person's progress against the time gone, so everyone sees who is on track.
Follow-up timing
Overdue follow-ups and quiet accounts show up in the attention list on their own, so nobody has to remember them.
Buying signals
Hiring, funding and technology changes that often come before a purchase. Each is listed with its evidence and a suggested pitch. A person decides what becomes a lead.
Response audit
How fast each first contact was, which replies were answered within 48 hours, and any silences. It reads real email, per person and region, and scores every lead for fit and reply quality.
Structured reviews
Self-rating, manager sign-off and a rolling history per person, written against the pipeline's own numbers.
Reports that drill down
Funnel, pipeline and revenue reports read from the live records, and every number opens the records behind it.
The proof library
Case studies, testimonials and samples, each linked to its account. Permission to publish, and any date limits, are recorded apart from whether the work is finished.
Case studies and quotes,
kept with the client's permission.
Case studies, testimonials and work samples stay linked to the account they came from. Four rules make sure we never use a story without permission.
Proof library: each case linked to its account, with its consent and embargo state beside it.
Bond · Proof library · Sample data from a demo workspace, not a client's numbers
- 01
A finished case isn't automatically published
A case can be complete and still not approved for external use.
- 02
Permission and timing limits are separate
A published asset may still carry limits on when, where and how it is used.
- 03
A case study isn't a reference
Permission to publish a story and permission to contact the customer are agreed separately.
- 04
One set of labels
Each case is tagged by industry, technology and service, so it's easy to find later.
This is the library behind our own proof pages. A quote or a case appears on this site only when its consent state allows it.
Prism sees what each lead became,
never who the customer is.
Prism needs to know what each lead became. It doesn't need to know who the customer is. Bond removes contact details before anything leaves it. Prism reads only what it needs through a limited connection, not a shared database.
- Channel and campaign context
- Geography
- Funnel stage history
- Disqualification reason
- Won status
- Names, emails and phone numbers
- Companies and linked accounts
- Raw descriptions and notes
- Deal values
Bond never fills a gap
with a guess.
A score shows its reasons. A failed data load never shows as all clear. A list can leave out items without evidence, and it says when it has. Every figure carries one of three labels. The screens stay simple, so the evidence stands out more than the design.
- SupportedThe evidence exists and the item shows where it came from.
- LimitedSome evidence, with the gap named beside the figure.
- No evidenceShown as missing. Never turned into a score that looks complete.
Prism and Bond are proprietary Vinove operating infrastructure and are not licensed standalone.
Frequently
asked.
Only where we run your sales pipeline. We find leads for your sales team, and sales accepts or returns each one. Bond then records each lead from first contact to customer and passes the result to Prism. On an engagement with no pipeline, such as a build or a redesign, Prism carries the work alone.
An MQL is a lead that met marketing's definition of a good lead. An SAL is one the salesperson agreed to work. That's the hand-off, and the number Prism uses for cost per SQL. An SQL is a qualified opportunity moving through the pipeline stages. Acceptance matters most, because it's the first point where sales, not marketing, has judged the lead.
It goes back with a clear reason: wrong fit, wrong timing, wrong contact or duplicate. Those reasons are kept where everyone can see them. The next marketing review can see what a rejected lead looked like. Then it can change the targeting, the rule for a good lead or the form. A rejection is evidence, and Bond keeps it.
No. Prism gets only what marketing needs, through a limited connection. That's the channel, campaign, location and stage history, the reason a lead was turned down, and whether it was won. Names, emails, phone numbers, companies, linked accounts, notes and deal values stay in Bond. Marketing learns what each lead became without learning who the customer is.
Yes, where we run the pipeline. The salespeople who accept and work the leads use Bond, with their own logins, targets and reviews. If you already have a CRM you want to keep, we can read acceptance from it instead. Tell us which, and the proposal will say how the hand-off works.
Nothing about your engagement is published unless your consent allows it. A finished case study isn't automatically ready to publish. Consent, timing limits (embargo) and permission to contact you as a reference are three separate records. Each one is agreed with you. Our own testimonials and case studies pages come from this library.
No. Bond is proprietary Vinove operating infrastructure and is not licensed or sold standalone. PixelCrayons runs pipelines in it when a client asks us to. You see it through the engagement, not through a licence. Your existing CRM stays yours. Bond is where we answer for the pipeline we run.
More on Prism, Bond
and how we work.
See Bond on a call
before you run a pipeline.
A walkthrough shows you the screens on a call. Where a pipeline is the right next step, the proposal says how Bond fits.
Reply within four business hours (typical) · Free · No retainer required
Last updated