Product

Journey Hub: the GovCon CRM built around the pursuit.

Journey Hub is samsearch's CRM for government contracting. Every opportunity you pursue becomes a journey: one place for the stage it is in, the tasks it needs, the documents it runs on and the people working it, so a pursuit is carried by a team rather than by whoever happened to find it.

A pipeline that knows what a pursuit is

Stages you name, a win probability on each one, and a forecast that is a by-product of working the board.

A journey opens the moment you decide to go after something, and it already contains the notice, the attachments, the agency and the dates. Nothing is retyped into it.

Columns you name and reorder, each with its own win probability
Total contract value and the weighted forecast, side by side
Deal value, period of performance and expected award date
Board, calendar and table views over the same journeys
Private journeys for the pursuits not everyone should see

For the argument behind the pipeline rather than the product that runs it, see capture and pipeline management.

Break a pursuit into work somebody owns

Every journey has its own board, so the pipeline card is a place work happens rather than a status field.

A due date on a pursuit tells you when it is too late. A task board on the pursuit tells you whether it is going to make it.

Tasks with an owner, a priority and a due date
Extracted requirements become tasks, so the matrix and the plan are one list
To Do, In Progress and Done, as a board, a calendar or a table
A My Tasks view across every journey you are on
Export any board

The requirements come from the solicitation shred, and they follow the amendment when one moves them.

Decisions in writing, on the pursuit

The reasoning behind a bid is worth more than the bid, and it is the first thing lost when it lives in somebody's inbox.

Comment where the work is. A thread on the journey is still there for the recompete, which is more than can be said for the email chain it replaces.

Comments and replies, on the journey and on individual tasks
@mentions that notify the person named
Reactions, for the acknowledgements that do not need a sentence
An activity log of what changed and who changed it

When the person holding a pursuit in their head moves on, the reasoning stays behind rather than leaving with them.

CommentsActivity log3 watching

DW
Dana Whitfield2d
Section L caps Volume I at 25 pages and we are at 31. Cutting the past performance appendix rather than the technical approach.
👍 3
MR
Marcus Reyes1d
Agreed. @Jordan the amendment moved two requirements, can you re-run the matrix before we cut anything?
👍❤️🎉👀✅🎉 12
JT
Jordan Tatenow
Re-run against amendment 0002. 38 of 38 requirements mapped, two due dates moved. Updated matrix is on the Documents tab.

Add a comment…@ to mention

Configure it to the way your team already works

Teams qualify differently, and a stage model imposed by a vendor is the fastest way to make a pipeline lie. Nearly everything here is yours to set.

Stages and fields

Name, reorder and add pipeline columns
A win probability on every stage
Deal value, period of performance and award date
Competition type, customer and business line

Views and filters

Board, calendar and table over the same journeys
Filter by type, owner, assignee, status and due date
Search by title or solicitation number
Choose which columns a table shows

Access and output

Owners and assignees per journey
Private journeys, visible only to the people on them
A My Tasks view across every pursuit you touch
Export any board or task list

Reporting nobody has to be asked for

Dashboards built from the journeys your team is already working, so the number leadership sees is the number the board is in.

The weekly pipeline review stops being a data-collection exercise the moment the pipeline is the source rather than the subject.

Goal attainment against a fiscal-year revenue target
Pipeline by stage, by competition type, by customer, by business line
Win and loss, and when awards are expected to land
Filters that apply across a whole dashboard
Reports you choose, on dashboards you compose

Values are spread across the period of performance rather than landing whole in the award year, which is the difference between a revenue forecast and a wish.

What lives on a journey

One record, and it is the record. Nothing here is somewhere else.

Questions

What teams ask before they move a pipeline into it.

What is Journey Hub?

Journey Hub is samsearch's CRM for government contracting. Every opportunity your team pursues becomes a journey, and that journey holds the pipeline stage, the tasks, the solicitation and its attachments, the contacts, the comments and the decisions. It is built around the pursuit rather than the deal, so the things it tracks are solicitation numbers, set-asides, NAICS codes, proposal due dates and amendments.

What is a GovCon CRM?

A GovCon CRM is a pipeline tool that understands government contracting objects rather than generic sales objects. A pursuit is not a deal: it has a solicitation number, a set-aside, an incumbent, a compliance matrix, a submission deadline that does not move, and amendments that change the requirements after you have started writing. A general-purpose CRM can be configured to approximate that, and then the configuration becomes a second product you maintain.

How is Journey Hub different from Salesforce or HubSpot?

The difference is what arrives in the record without anyone typing it. A journey opens with the notice, its attachments, the extracted requirements, the agency and the dates already in it, because samsearch found and read the opportunity in the first place. Salesforce and HubSpot are excellent at the pipeline mechanics and know nothing about a solicitation, so the work of getting a pursuit into them is the work.

How does Journey Hub forecast pipeline?

Every stage carries its own win probability, so a journey with a deal value contributes its weighted share automatically. The board shows total contract value and the weighted figure side by side, and both update the moment somebody moves a card. That is the only way a forecast stays true: it is a by-product of working the pipeline rather than a spreadsheet somebody refreshes on the Friday before a board meeting.

Can my whole team work in the same pursuit?

Yes, and that is what a journey is for. Journeys are shared across your organization by default, with an owner and assignees, comment threads with replies, @mentions that notify the person named, emoji reactions for the acknowledgements that do not need a sentence, and an activity log recording what changed and who changed it. Pursuits that should not be visible to everyone can be marked private.

Can I customize the pipeline stages?

Yes. Columns are yours to name, reorder and add to, and each one carries its own win probability, so the board matches how your team already qualifies work rather than a stage model we picked. The same journeys can be read as a board, a calendar or a table, filtered by type, owner, assignee, status, due date or visibility, and searched by title or solicitation number.

Does Journey Hub track tasks and deadlines?

Yes. Every journey has its own task board with To Do, In Progress and Done columns, and each task carries a priority, a due date and an assignee. Tasks can be read as a board, a calendar or a table, and a My Tasks view collects everything assigned to you across every pursuit, which is the view most people live in.

Where do the tasks come from?

You write them, and samsearch generates them. When a solicitation is shredded, each extracted requirement can become a task on the journey, so the compliance matrix and the work plan are the same list rather than two documents that drift apart. When an amendment moves a requirement, the re-run shows what changed and the task follows it.

How do leadership and stakeholders get visibility?

Through dashboards built from the same journeys the team is working, so nobody is asked for a status update. Reports cover goal attainment against a fiscal-year target, pipeline by stage, by competition type, by customer and by business line, win and loss, and when awards are expected to land. Filters apply across a whole dashboard, and any board exports.

Do the solicitation and its attachments come into a journey automatically?

Yes. Opening a journey from an opportunity pulls in the notice and its attachments and indexes them, so they are searchable and can be asked questions in plain English straight away. Attachments stay in sync as amendments post. You can also upload your own documents, such as past performance write-ups or price backup, and they are indexed the same way.

Which opportunities can become a journey?

Anything samsearch covers: federal contract opportunities, state and local, GSA eBuy, DLA DIBBS, grants, SBIR and STTR, agency forecasts and recompetes. You can also start a journey from a document you upload or from nothing at all, which is what teams do for a pursuit that arrived by email or through a partner.

Is Journey Hub a separate product?

No. It is part of the samsearch platform and it is where the rest of the platform lands: an opportunity found by the recommendations, read by the analysis, worked as a journey, and responded to from inside it. That is the reason a journey opens already populated, and it is why there is nothing to integrate between the parts.

Put your pipeline where the work is.

See Journey Hub against your own pursuits, with your stages and your team on it.

Request a demo