E-FACTS — E-receipt management companyE-FACTS — E-receipt management company
Product

Users & personas

Who E-FACTS serves — shoppers, retailers, and internal operators

Users & personas

Product decisions start from who is trying to finish a job. Use these personas to frame specs, copy, and prioritization — not as rigid marketing segments.

Primary: Shopper (consumer app)

Job: Keep proof of purchase usable — returns, warranties, spend recall — without paper clutter.

TraitImplication
Time-poor at the counterBind / capture flows must be short and recoverable
Returns anxietyReturn windows and line-item clarity beat vanity dashboards
Trust-sensitiveAuth, UCI / last4 bind, and privacy language must be plain
Mixed finance literacyCurrency always tabular; avoid jargon in Analysis

Success looks like: “I found the receipt and knew what I could return in under a minute.”

Secondary: Retail partner / ops

Job: Issue structured e-receipts and understand redemption / eco signals without custom one-offs.

TraitImplication
POS constraintsCapture must tolerate incomplete events and retry safely
Brand riskEco claims only when backed by real signals
Integration costPrefer stable APIs and documented schemas over bespoke portals

Internal: Company users (this docs site)

RoleNeeds from Product docs
Founder / ExecNorth star, surfaces, metrics — no implementation noise
Product / DesignIA, principles, lifecycle, writing tone
EngineeringClear ownership of surfaces + links into Engineering section

Anti-personas (do not optimize for)

  • Screenshot collectors who never need structured line items
  • “Green badge” marketing that cannot cite a real offset or paper-saved signal
  • Internal tools that leak into the consumer tab bar

How personas affect the 4 tabs

TabShopper job
HomeOrient, act on alerts, jump into Bills / Analysis / Offers
My BillsVault of receipts — return, warranty, line detail
AnalysisUnderstand spend by category / time
OffersDiscover and redeem retailer offers

Profile / account stays in a drawer, not a fifth tab — see Information architecture.

On this page