PanoramaSep 2024 — Nov 2024Co-founder, Designer & Frontend Engineer

Organizing unstructured work data

Who's working on what and how, surfaced as readable team context from the unstructured signal across GitHub, Slack, and the rest.

Team: Me (Front-End & Design) • Co-Founder (Back-End)
Stack: Next.js (web)
Audience: Engineering teams

Timeline: Sep 2024 — Nov 2024
Scope: Connective-tissue product for software teams—ingested GitHub, Slack, and adjacent tools and surfaced team-level context as ranked feeds and ambient summaries.
Responsibility: Owned design and front-end end-to-end, plus the long tail of 0→1 work: landing page, onboarding, integrations UX, customer interviews, fundraising decks, and early sales outreach.

Context

Where does "who's working on what and how" live? In someone's head, usually. Software teams generate enormous amounts of unstructured signal—pull requests, Slack threads, Linear comments, design files, meeting notes—but the picture stays trapped in chat history. Panorama set out to be the connective tissue across those signals, surfacing team-level context as a readable feed rather than another dashboard to babysit.

Approach

Co-founded the company and owned design and front-end end-to-end alongside the long tail of 0→1 work—landing page, onboarding, integrations UX, internal tooling, customer interviews. The product surface ingested GitHub, Slack, and adjacent tools and surfaced team-level context as readable summaries, ranked feeds, and ambient notifications rather than another dashboard to babysit.

Impact

Shipped the first version of the app and signed an eager first pilot customer. Spent the run wearing every other hat too—fundraising decks, sales outreach, customer interviews. Left when my personal runway ran out before the next round closed. The product proved out; the business didn't make it past seed.

What does Panorama actually do?

Panorama integrates with tools like GitHub and Slack, organizes the unstructured work data they generate, and presents it in a breathable, consumer-grade surface—not another enterprise dashboard to babysit.

What does the company view show?

A summary of every team—engineering, design, the rest—against the goals they share. Alignment becomes a daily-to-yearly artifact instead of a quarterly slide deck: who's working on what, what's blocking it, and how today's work ladders up to the year's commitments.

What does the team view show?

A view into how a team is actually collaborating, with each individual's work rolled up underneath. The standup, the pull-request feed, the Slack catch-up—folded into one surface so a manager doesn't have to stitch them together by hand.

What does the individual page do?

Each person gets a page closer to a MySpace profile than a LinkedIn one—a place to present their most authentic self at work. Shipped work, in-flight projects, how they think and collaborate; not a title and a job description.

Can you make your own widgets?

Anyone—individual or team—can spin up an AI-generated widget tailored to what they actually need. To-do lists, on-call rotations, office-hours availability, bug-tracker rollups, SEV-free streaks, emoji leaderboards for who got the most thanks this week, polls for the next offsite. The widget vocabulary is wide open because the underlying data already is.

More work

All work