PART 1

Customer/User Job-to-be-Done or Problem

Gazelle clients are expecting the most update as well as accurate contact information for companies on the platform 

Value to Customers & Users

The microservice will combine several signals to evaluate the validity of a contact.

Value to Lightcast

Increase customer retention and sales conversion.

Target User Role/Client/Client Category

Gazelle clients

Delivery Mechanism

Gazelle platform

Success Criteria & Metrics

Designing a microservice that combines email pinging, linkedin status, and email sourcing as a combined confidence score, i.e. have all the technical requirements and business rules established.

Aspects that are out of scope (of this phase)

PART 2

Solution Description

Early UX (wireframes or mockups)

<FigmaLink>

Non-Functional Attributes & Usage Projections

Consider performance characteristics, privacy/security implications, localization requirements, mobile requirements, accessibility requirements

Dependencies

Is there any work that must precede this? Feature work? Ops work? 

Legal and Ethical Considerations

Just answer yes or no.

High-Level Rollout Strategies

• Initial rollout to [internal employees|sales demos|1-2 specific beta customers|all customers]

  • If specific beta customers, will it be for a specific survey launch date or report availability date 

• How will this guide the rollout of individual stories in the epic?

• The rollout strategy should be discussed with CS, Marketing, and Sales.

• How long we would tolerate having a “partial rollout” -- rolled out to some customers but not all

Risks

Focus on risks unique to this feature, not overall delivery/execution risks. 

Open Questions

What are you still looking to resolve?

Complete with Engineering Teams

Estimated Costs

Direct Financial Costs

Are there direct costs that this feature entails? Dataset acquisition, server purchasing, software licenses, etc.?

Team Effort

Each team involved should give a general t-shirt size estimate of their work involved. As the epic proceeds, they can add a link to the Jira epic/issue associated with their portion of this work.