Clay for CRE assessors
Multi-source verification flags conflicting values across assessor and tax collector portals.

Turns Linear cycles into client portals so PMs stop rewriting status updates.
Dev agencies using Linear with external clients
Basecamp · Jira · Linear
The issue isn't access — clients don't need to be in Linear. The issue is translation. Linear data is internal by nature, and turning it into something a stakeholder actually understands is tedious work that falls on someone every sprint.
Alignear sits on top of your Linear workspace and handles that layer: - Automatic cycle reports generated from your Linear data - Custom reports with any filters you need - Secure client portal — clients open a link, no account required - AI agent inside Linear — tag @alignear in any ticket comment to capture tickets as meeting notes, more capabilities coming
Built this solo. It's live and working in production. Would love feedback from anyone who's dealt with this problem — particularly interested in hearing how larger teams handle client communication today and where the current solution breaks down.
alignear.com
Multi-source verification flags conflicting values across assessor and tax collector portals.
Another gated founder community landing page with a pixel art rocket.
Reports + dashboards + distribution in one place, but oversells against entrenched BI stacks.
Automated client reports from file activity without requiring Git or timesheets.
Yet another audit tool bundling Lighthouse, securityheaders.com, and basic robots.txt checks.
The one-click PowerPoint export is the real selling point — it packages KPIs, timelines and qualitative stories into slides using pptxgenjs, which actually solves the tedious manual rebuild nonprofits hate. The repo shows care (type-safe indicator calculations, Vite chunking, tests), but to go beyond an MVP it needs robust templating, spreadsheet/connectors and a reusable data model for different orgs and donor formats.