Case study · Planning and time-tracking software for Jira

From Jira signal to product-aware outreach

Tempo sells a portfolio of products used in and around Jira. Knowing a company uses Jira doesn't tell you which Tempo product is relevant. We built the decision layer that answered it.

Download detailed case study (PDF)PDF · 6 pages

Case study · B2B software

Tempo Software, planning and time-tracking software for Jira.

980 leads active in campaigns
30–40% passed the Jira gate
Campaigns live
General, Timesheets and Structure — in production from late September 2025
The gate
Jira presence was a hard requirement; records failing it did not proceed to research
The design
One initiative selected per company, matched to a Tempo product and feature before any message was written

The problem

Jira was a gate, not the message

Knowing a company uses Jira is useful, but it doesn't tell you whether the conversation should be about time tracking, capacity planning, portfolio structure, or something else in Tempo's portfolio.

Three Jira users, three different conversations

  • One company launching a major new product and coordinating work across several teams.
  • Another expanding headcount and struggling with resource allocation.
  • A third improving project reporting and executive visibility.

All three may be legitimate Tempo prospects, but the most relevant product, feature and message can differ for each. Early testing showed only 30–40% of incoming leads passed the Jira-presence check — so Jira became a hard gate that improved the population entering the more expensive research stages. But the gate only answered “could this be relevant?” It did not answer “why should this company care?”

What we built

A decision layer before the email

  1. Multi-source initiative researchEvidence about company initiatives from websites, third-party sources and LinkedIn — substantive initiatives, not random personalization facts.Define
  2. Initiative scoringProduct fit, outcome alignment, recency, evidence confidence and category priority — one best initiative selected per company.Qualify
  3. Product and feature matchingDetailed product descriptions written for the research logic to compare against, deliberately designed to reduce hallucination.Contact
  4. Portfolio reasoningThe general campaign recommended one or two relevant Tempo products before writing; known-product campaigns kept product context fixed.Launch
  5. Message generated lastOutbound was constructed only after the company, initiative, product and feature decisions were made.Launch

The pipeline connected an upstream prospect source, Clay and Smartlead, supporting several simultaneous campaign paths. Capacity Planner routed through the same path once Jira-qualified prospects were available — and waited for qualified data rather than launching on schedule.

Production realities

A workflow is an implementation. A production system has met reality.

  • Source-data formats changed and fields didn't always arrive as expected; formulas and classification logic were adjusted to the data actually arriving.
  • Counting differences between stages were traced from the upstream source through Clay into Smartlead to explain where records went.
  • TCA produced a detailed walkthrough of the Clay implementation so the system could be understood and operated beyond its builder.

AI's role was constrained: it never received an empty prompt asking it to write a personalized email. The surrounding research system supplied the evidence and commercial context — interpreting initiatives, evaluating fit, ranking competing initiatives and selecting features.

Don't personalize the sentence. Personalize the reason.
Next caseBlack Box Intelligence: turning restaurant-market signals into executive outreach →

Related reading

A practical guide to the research and system-design decisions behind work like this.

Why a Clay build is not a complete GTM system

Let's discuss your GTM challenge.

A short, no-obligation introductory conversation.

Schedule a conversation