About LinkBoard
A small product for a boring problem: the links, dates, and decisions for a piece of work live in four different places, and none of them explain each other.
Why we built it
We kept losing the same things. A client’s brand folder. The one academic paper that actually supported the argument. The “we already decided this” link from a meeting two weeks ago. The tools were all fine on their own. The cost was the switching: open the browser, search Slack, check the calendar, then reconstruct the story from memory.
LinkBoard is our attempt to put those pieces on one desk. Not a giant knowledge graph. Not a social feed. A directory you can name after a real project, links you can annotate in plain language, a calendar for the dates that belong to that work, and a small poll when a group needs a yes or no.
If that sounds modest, good. Most “productivity” products fail by trying to replace everything you already use. We would rather be the place you park the five URLs that keep the project honest.
What we care about
Context next to the URL. A bookmark without a note is a riddle. We nudge people to write the sentence they would have said out loud: who it is for, when to use it, what to ignore.
Private by default. A lot of useful collections should never be public. Contracts, internal notes, half-finished research. Sharing is a choice, and public directories are held to a higher bar: a real description, no junk, no deceptive titles.
Maintenance over hoarding. Saved links rot. We write about weekly and monthly reviews because a shorter, accurate list is more useful than a museum of dead tabs. The product will not magically keep itself tidy. The habits in the docs are part of the design.
No fake social proof. We do not invent review counts or stock-photo testimonials. If someone finds LinkBoard useful, they can tell a colleague. If they do not, the free plan is easy to leave.
Who it is for
Freelancers who hand the same three folders to every client. Students who are tired of reconstructing sources the night before a paper. Small teams who do not need an enterprise wiki, but do need one shared list that is not a spreadsheet named FINAL_v7.
It is less of a fit if you want a full project-management suite, a reading-later app with offline articles, or a public search engine of the whole web. Those products exist. We are the middle drawer: the stuff you need again, labeled.
How the company works
LinkBoard is an independent web app. Accounts, directories, and calendar data are stored with Supabase. Transactional email is sent through Resend. Paid plans go through Stripe. Advertising, where it appears after you are signed in and there is real content on the page, is served by Google AdSense and respects the cookie choice on the site.
We would rather keep the free plan useful than force a trial wall on day one. Ads on logged-in pages with actual links and events help pay for that. Public marketing pages are written to explain the product, not to host a grid of ads.
Questions, policy reports, and deletion requests go to admin@linkboard.io. We typically reply within one or two business days. The contact page has what to include so we can actually help.
If you want to look around
The features page describes what is in the app today. The docs are written as working notes, not slogans. The blog is for longer habits: how to review a list, how to hand work to a client, how to cite what you saved.