Skip to content
CLIENT STATUS · JIRA & LINEAR

Your team keeps Jira or Linear. Your client gets the project state.

ClientLens turns the work already happening in Jira or Linear into a focused, branded client status page. Read-only connection, explicit visibility, and a client preview before you publish.

Free to connect, build & preview. Start the 14-day no-card trial when you're ready to publish. $15/mo after trial.

  • Read-only Jira & Linear
  • You choose visibility
  • Preview before publish
acme.atlassian.netACME · SPRINT 24BACKLOGACME-142Safari onboarding500MP2ACME-141Audit logs UIJP3IN PROGRESSACME-138Okta SSO —assertionsMP1ACME-134DB read replicaKP2REVIEWACME-127Per-page passcodeJP2DONEACME-129Custom domainsKP1INTERNAL ONLYAcme Corp · Q2 deliveryUPDATED 2 MIN AGO · FROM JIRALIVE12SHIPPED4IN PROGRESS2IN REVIEW5UP NEXTIN PROGRESSSingle sign-on with OktaTarget: Jun 6IN PROGRESSCustom domains on client pagesShipped May 24DONEPer-page passcodesQA this weekIN REVIEWacme.clientlens.appview-only · Acme teamWHAT YOUR CLIENT SEES

Works with the tools your team already lives in

  • Jira CloudRead-only
  • LinearRead-only
  • AsanaOn the roadmap

The visibility gap

The project moved.
The client's picture of it didn't.

Internal project state can change continuously. Client understanding often changes only when someone sends the next update. ClientLens gives that client-facing state a focused surface connected to the source work.

01

Two clocks

The team sees project changes as they happen. The client sees the last state someone communicated.

02

Too much internal context

Assignees, comments, labels, raw workflow detail, and technical context help the team operate. They should not become the default client interface.

03

A second status state

Every manual email, screenshot, deck, or message recreates project state somewhere else, and that copy starts aging as soon as the work changes.

How it works

Keep the operating workspace.
Publish the client view.

  1. 01YOUR TRACKERACME-138Okta SSO — assertionsIn progress · @mayaACME-141Audit logs UIBacklog · unassignedCLIENT PAGEAcme · Q2Single sign-on (Okta)IN PROGRESSCustom domainsDONEREAD-ONLY OAUTH
    Connect

    Connect Jira or Linear read-only

    Your tracker stays the source of truth. ClientLens reads the project data it needs without writing back to Jira or Linear.

  2. 02EVERYTHING IN JIRAACME-138 Okta SSOINTERNAL Migrate prod DBACME-129 Custom domainsINTERNAL @maya 1:1 notesACME-134 DB read replicaACME-127 Per-page passcodeINTERNAL Pricing experimentINTERNAL Security auditDENY BYDEFAULTCLIENT SEESOkta SSOLIVECustom domainsLIVEPer-page passcodeLIVE
    Shape

    Choose the client-facing view

    Map the project or epic, control visibility, add client-facing overrides where useful, and keep internal working detail outside the client surface.

  3. 03Acme Corp · Q2 deliveryUPDATED 2 MIN AGOLIVESingle sign-on (Okta)IN PROGRESSCustom domainsDONEacme.clientlens.app
    Preview & publish

    Check the client view before sharing

    Preview exactly what the client will see. When it looks right, start the trial and publish the branded page. Add a passcode when the page needs another access boundary.

Demo

See the path from source project to client-facing status page.

In this demo

  • Read-only Jira or Linear connection
  • Explicit mapping and visibility controls
  • Preview the client-facing view before publish

Running time

01:32

Trust by construction

A client-facing view needs explicit boundaries.

  • Read-only source access

    ClientLens reads Jira or Linear without becoming another writer to the source project.

  • Deny by default

    Nothing is included in a client page until it is mapped into that page and survives the visibility rules. Exclude rules win when rules conflict.

  • Focused public projection

    The public page receives a separate client-facing projection. Assignees, internal comments, labels, and raw descriptions are not part of that projection.

  • Preview before publish

    Check the exact client-facing title, status, dates, progress, blockers, and notes before sharing the page.

INTERNAL · ACME-13811Assignee · @mayaInternal comment threadStatus · In progressStory points · 5Raw descriptionTitle · Okta SSOLabel · @internal-onlySprint · 24Target date · Jun 6Engineering notesLinked ticketsPUBLICPROJECTIONON THE CLIENT PAGE3TITLEOkta SSOSTATUSIn progressTARGETJun 6internal detailnot included inthe public projectionAUDIT TRAIL10:24 · visibility saved10:23 · preview as client09:51 · scope set to Acme09:30 · source connected09:30 · org created

The outcome

One source of truth. A clearer client view.

  • Keep one operating workspace

    Your team stays in Jira or Linear. ClientLens adds the client-facing status surface without becoming another delivery tool to maintain.

  • Share the state, not the workspace

    Give clients the status, target dates, progress, blockers, and update they need while internal working detail stays outside the client surface.

  • Control the handoff

    Preview before publishing, share a branded URL, add a passcode when needed, and keep public pages out of search indexes.

Pricing

One plan. Honest price.

Connect your tools, build pages, and preview exactly what your client will see — all free. You only need an active subscription to publish a page live.

ClientLens

Standard

Single plan
$15/ month

14-day free trial · cancel anytime · billed monthly

Free to connect, build & preview · you only pay to publish · cancel in one click

Everything included

  • Unlimited client pages
  • Jira Cloud & Linear integrations (read-only)
  • Branded pages with your logo & color
  • Deny-by-default visibility engine
  • Preview-as-client mode
  • Page-view signals (your client viewed this)
  • Optional per-page passcode
  • Audit log

FAQ

The boundaries, before you share a client page.

Still unsure? Email us and ask about your workflow.

No. ClientLens is a read-only layer on top of your existing Jira or Linear. Your delivery team keeps working in the tool it already uses.

From the founder

“I built ClientLens around a simple boundary: internal project management and client communication are different jobs. The team should keep the detail it needs. The client should get the project state it needs.”
Rojan Acharya, founder of ClientLensRojan AcharyaFounder, ClientLens · hi@clientlens.app

Give clients the project state

Keep the workspace.
Publish the client view.

Connect, build, and preview free. Start the trial when you're ready to publish.