Vdar
Jason
About explains why Vdar began. Founder Journal is different: it is where I will record what is happening now, what is still unfinished, and why certain product decisions are being made as Vdar moves through Phase 0.
Vdar already has an About page, and that page has a clear job. It explains the origin of the product: the frustration, the repeated work, and the reason I started building a better job-application workflow. A permanent story should not change every week. If I keep adding every new thought there, the page becomes noisy and less useful for someone who simply wants to understand where Vdar came from.
Founder Journal exists because company building is not static. Some weeks are about shipping visible pages. Some weeks are about fixing the less glamorous parts: trust, pricing clarity, content structure, browser checks, and the small details that make the product feel real. These notes should not pretend every decision was obvious from the beginning. They should show the work as it is: a series of choices, corrections, and trade-offs.
Vdar is still in Phase 0: launch, retest the full workflow, and earn the first real users. That means Founder Journal should be careful with language. Live features should be described as live. Planned ideas should be described as planned. If a number is not verified, it does not belong here. This channel only works if it makes the company easier to trust, not louder.
The long-term point of Founder Journal is simple: show the thinking behind the product without turning it into marketing theatre. A serious job seeker should be able to read these notes and understand why Vdar charges, why it avoids a low-quality free tier, why it cares about complete application kits, and why the product is built slowly enough to protect quality. The story is not just what Vdar is. It is how the product earns the right to be trusted.
About is the stable origin page. Founder Journal is the ongoing record of product decisions, company progress, lessons, and honest status updates.
Yes, but only when they are clearly framed as in progress or planned. Founder Journal should not present roadmap ideas as shipped product.
Vdar asks users to trust the quality of its workflow. Public founder notes make the thinking behind that workflow clearer and easier to evaluate.