Posts by zerosoft
The zerosoft team writes these posts. 111 posts so far.
Giving feedback on video: a 3-minute review with Rec
How to review a design or a pull request in a short video with a structure people understand without a meeting, and how to run it in Rec with time-stamped comments, restricted access and a Track issue.
NPS survey in Forms: template, logic and how to read it
How to build an NPS survey in Forms with the built-in template: a 0 to 10 question, follow-ups by score, hidden fields and how the result is calculated.
A robot behind a login, without leaving your password in the open
How to make a robot sign in to a site with username, password and 2FA, keep the session between runs and avoid exposing private data. Steps and real limits of zerosoft Robots.
Impact and effort matrix: how to decide what to do first with your team in Board
A priority matrix in Board in 45 minutes: criteria written before anything is placed, a ready template, hidden voting and quick wins turned into Track issues.
Note templates people actually use: six to set up today
How to design short note templates, which six are worth having, and how to save, name and find them in Notes, including the real limits.
What to do with a feature request that arrives in chat
A four-step method for answering feature requests without overpromising: tag in Chat, link to a Track issue, count distinct customers, and tell them when it ships.
Quarterly sales plan: from a revenue goal to meetings per week
How to turn a revenue goal into per-person quotas and a weekly meeting count, with a worked example and how to load it into zerosoft CRM.
How to share your booking link so people actually use it
Where to put your Cal link (email, signature, website, campaigns), how to prefill details, track where each booking came from, and when a secret or single-use link fits better.
How to build a sales forecast a small team can defend
Categories, quotas and per-person submissions: how to turn a pipeline full of deals into a monthly number you can trust, with examples in zerosoft CRM.
A short link that doesn't work: how to diagnose it in five minutes
A troubleshooting guide for broken short links: the most common causes, how to tell them apart from the outside, and what Link shows in each case, with a checklist to copy.
From a web directory to companies in your CRM: a prospect list built by a robot
How to walk through a paginated public directory, keep only the new rows and load them as companies into the CRM without duplicates, using zerosoft Robots. Steps, settings and real limits.
A customer journey map on a whiteboard: a 5-stage template and how to turn it into tasks
How to build a customer journey map in Board with real data from your team: the 5-stage template, a 60-minute session, voting on opportunities and turning stickies into Track issues.
Digitizing receipts and paperwork with your phone: a ten minute a week method
How to go from the shoebox to notes you can actually find: taking the photo, scanning several pages into one PDF in Notes, naming, tagging and searching. With what text reading does today and what it still doesn't.
Migrate from Calendly to Cal: event types, hours, bookings
How to move from Calendly to Cal with a personal access token: what imports (event types, questions, availability, upcoming bookings) and what to check.
How to migrate from Evernote to Notes with .enex files
Move your Evernote notebooks into Notes: how to export the .enex, what comes across (attachments, tags, dates, to-dos), what gets lost and what to check after.
How to migrate from Excalidraw to Board (and what about Miro)
Import your .excalidraw files into Board in bulk: which elements and images come across, what gets dropped, the limits, and what to do if you use Miro.
Migrate from Intercom to Chat: bring your conversations
How to move from Intercom to Chat: pull the JSON from Intercom's API, what imports (people, messages, status), what doesn't, what to check first.
Migrate from Linear to Track: what imports and how
How to move your Linear issues to Track with an API key or a CSV export: what comes across (teams, cycles, labels, comments), what stays behind, what to check.
How to migrate from Pipedrive to the zerosoft CRM
Move Pipedrive persons, organizations, deals, pipelines, custom fields and activities into the CRM with your API token, and what to check once it finishes.
How to test an AI agent before it talks to your customers
A four-step method to test a support agent: saved tests graded by an AI judge, simulated conversations, replays of real chats, and versions with a draft.
Human approvals in a flow: pause, ask and continue
How to put a person in the middle of an automation: Flow's Approval node, what happens when nobody answers, how to use the comment, and a full example with discounts.
Migrating from Notion to Docs: two paths and a checklist
How to move your Notion workspace to Docs with the Markdown and CSV export or an API integration: what travels, what to review and in what order.
Charging for a booking with Stripe in Cal: a step-by-step guide
How to charge for consultations and sessions from your booking page with your own Stripe account: setup, what happens when the guest doesn't pay, and how refunds work.
One link, several destinations: country, device and A/B tests
How to send each visitor to the right place with a single short link: country and device rules, weighted A/B tests and app deep links, plus the exact order Link resolves them in.
Incoming webhooks in Flow: receive, protect and reply
How to build a URL that other services call: method, header authentication, reading the body, replying with your own status code, and the limits that exist today.
Team brainstorming: a 60-minute script with stickies, a timer and hidden votes
How to run an ideas session in Board: a well-built question, a silent writing round, grouping, dot voting and stickies that end up as issues in Track.
301 or 302 on a short link: what actually changes
What 301, 302, 307 and 308 redirects mean, what Google does with each, why browser caching matters more than SEO for a short link, and what Link does when you pick 301.
Help articles for two readers: your customer and your bot
How to write help center articles that answer in the first lines, match the words customers actually type and work for the Chat bot, using the help center built from published Docs pages.
How to write the brief and the knowledge for a support agent
A brief template for an AI agent, how to write Docs pages the search will actually find, and a test method with real questions before you publish.
A help center for your customers, built with Docs
How to set up a public help center with Docs: collections, articles that search can find, the Was this helpful vote, the Help tab in the Chat widget and AI answers. With the limits in plain view.
Zero bugs on a small team: triage, deadlines and one rule
How to run a zero-bug policy with three to ten people: a rule with two exits, deadlines by priority, a weekly on-call rotation and Track's triage queue for whatever arrives through Chat or Flow.
How to write an issue someone can actually finish
Rules for issue titles, descriptions and size, three plain-text templates for bugs, tasks and investigations, and how to use sub-issues, relations and estimates in Track.
When an AI agent should hand the conversation to a person
Five situations where a support or sales agent has to hand off, how to set up each one in Agents, and what to review every week to tune the rules.
When a flow fails: retries, error branches and re-runs
Which errors are worth retrying, when to continue and when to stop, how to build an error flow that alerts you, and how to re-run from the failed step without repeating the ones before it.
Rule-based lead scoring: ten rules you can explain in a meeting
How a small team can build lead scoring from property rules and recent-activity rules, check it against deals it already won or lost, and turn the score into tasks with workflows.
Fewer no-shows: reminders and booking rules in Cal
Why people miss meetings they booked themselves, and how to cut it with Cal: a confirmation with an .ics file, a reschedule link, a reminder sequence with templates, booking rules and the No-show mark.
Track your competitors' pricing with a robot and a flow
A robot that reads your competitors' pricing pages every day, keeps the history in a spreadsheet and alerts you when something changes or when the page gets redesigned. Step by step with Robots and Flow.
Meeting notes that end in tasks
A meeting notes format in Docs with decisions and action items that have an owner and a date, a tracking table between meetings, moving the big items to Track and an automatic page for every Cal booking.
How to organize your notes: four notebooks, a few tags and search that finds things
A note system you can set up in an afternoon: four PARA-style notebooks, a short tag list, pinned notes for daily use and full-text search. With the steps in Notes and what it still lacks.
What to automate first: five flows for a small team
A rule for picking what to automate, and five concrete flows you can build in Flow from templates: leads, bookings, deals, bugs from chat and billing.
What data a booking leaves behind, and where it goes
The full map of a booking in Cal: what's stored in the row, which copies go out to email, Google Calendar, the CRM, webhooks and Stripe, and how to answer a deletion request. With the gaps stated.
What happens to your short links if the shortener shuts down
What the goo.gl and Firebase Dynamic Links shutdowns left behind, and a four-step plan so your short links outlive any provider: your own domain, export, re-import and self-hosting.
Saved replies: five tone rules and twelve support templates
How to turn a support tone guide into rules you can check line by line, plus twelve saved replies ready for Chat, with the automatic actions worth attaching to each one.
A retro on a whiteboard: format, a 45-minute script and what to do with the actions
How to prepare and run a team retrospective in Board: three formats, a minute-by-minute script, dot voting and action items that land in Track. Including how to work with a board that doesn't do live co-editing yet.
Sales follow-up: a five-touch sequence that stops on its own
A two-week follow-up cadence with emails, a task and business-day waits, the copy to paste, and how to set it up with sequences in zerosoft CRM.
Backing up a self-hosted zerosoft: one database, one folder, one .env
A self-hosted zerosoft is a SQLite file, an uploads folder and an .env. How to copy them while the app runs, store them off the server and test a restore.
One codebase, two databases: a local SQLite file or Turso
zerosoft runs on a SQLite file on disk or on a remote Turso database, switched by one environment variable. How it works in the code and how to choose.
Docs vs Notion: what each does today
Notion leads on real-time editing, databases, AI, import and export, integrations and mobile. Docs is a small, self-hostable editor for wikis and notes. Who it fits.
zerosoft CRM vs HubSpot: what each does today
Where HubSpot is far ahead, where zerosoft CRM holds up, and who should stay with HubSpot. The gaps are listed, not hidden.
Link vs Bitly: what each does today, and when to stay with Bitly
Where Bitly is ahead, where Link is, and who should switch or stay: features, ecosystem, ownership and trade-offs.
Cal vs Calendly: what each does today
Where Calendly is ahead, where Cal holds up, and who should switch or stay. No invented benchmarks.
One suite or a separate tool for each job: the trade-offs
Shared login, one database and one search, or specialized products that go deeper. What zerosoft's apps share today, what they don't, and when to pick specialists.
Versioned migrations without an ORM: a baseline, a list and one table
How zerosoft changes its SQLite/libSQL schema with numbered migrations in plain TypeScript, why each one must survive running twice at once, and the SQLite trap that can delete data.
Chat vs Intercom: what each does today
Intercom is far ahead on AI, channels and integrations. Chat is a self-hostable webchat inbox with SLAs and CSAT. Who should switch, and who shouldn't.
Static lists, dynamic lists and custom fields in zerosoft CRM
How to segment contacts with static lists, dynamic lists, saved views and custom fields: what each is for, its limits, and rules to keep the data clean.
Password, expiry and click limits on short links: when to use each
Use cases for password-protected, expiring and capped links in Link, what visitors see when a link closes, and where QR codes fit in.
Embedding Cal on your site: inline, popup, Google Meet and reminders
How to put your Cal booking page on your own site, connect Google Calendar for Meet links, and check that cancel links and 24-hour reminders go out.
Why the README lists what each product is missing
Every product in the README has a Known gaps line next to its features. Why we publish them and how it changes what we build.
Rate limiting without Redis: one table and one UPSERT
How zerosoft rate-limits its API and public endpoints with a fixed-window counter in the same SQLite/libSQL database, and when that stops being a good idea.
Track vs Linear: what each does today
Where Linear is ahead, where Track holds up, and who shouldn't switch. Written by the people who build Track, gaps included.
A 30-minute weekly CRM review
A weekly routine for small sales teams: one dashboard, a saved view, two filters, two dynamic lists and one rotating report. What to look at and in what order.
UTMs without the spreadsheet: a naming convention for small teams
A short UTM naming convention, and how to run it in Link with the UTM builder, tags, bulk create, per-link CSV export and 7/30/90-day comparisons.
How Cal handles time zones: wall clocks, UTC and DST
What Cal stores in UTC, what it keeps as wall-clock time, how slots survive DST changes, and how emails and .ics invites reach the guest in their own time zone.
Self-host or zerosoft Cloud: a checklist
Self-hosting zerosoft costs $0 and starts with docker compose. Running it well means HTTPS, Google OAuth, email, cron, backups and domains. The list, so you can decide.
zerosoft webhooks: what's signed, how to verify it, what happens on failure
Events, an HMAC-SHA256 signature in a Stripe-style header, retries with backoff for about 15 hours, and an SSRF guard. Plus a Node verifier you can paste.
An internal wiki with Docs, step by step
How to build a company wiki with Docs: a page tree, [[ links, templates, comments, sharing and trash, plus the limits to know before you start.
Pipeline hygiene for small teams: eight rules for an accurate CRM
How to design stages, when to use more than one pipeline, what to do with stale deals and how tasks keep deals moving, mapped to what zerosoft CRM does.
Moving from Bitly to Link: what the import brings and what it leaves
Import Bitly links into Link by API token or CSV: what comes across, what doesn't, how back-halves are kept, and the right order for custom domains.
Buffers, minimum notice and booking windows in Cal
How weekly availability, buffers, minimum notice, booking windows and blocked slots work in Cal, and the defaults we suggest for each.
Open core at zerosoft: what's AGPL, what's in /ee, and why
Everything in the repository is AGPLv3 except one folder, /ee. What lives there, what its draft license says, what's built today and how we drew the line.
The REST API v1 by example: personal keys, curl and real errors
Create a zs_ key, shorten links, read click stats and create CRM contacts and deals from a script. Every example matches the route handlers, errors included.
Support SLAs in Chat: a one-page setup
How to set response-time targets in Chat with SLA policies, assignment rules, office hours, priorities, canned responses and CSAT, and how the SLA clock counts.
CRM workflows that create follow-up tasks
How to use zerosoft CRM workflows to create follow-up tasks: the real triggers and actions, five recipes for small teams, and the limits to know.
Building a link-in-bio page with Link, and what it can't do yet
Your /@handle page in five minutes: title, bio, avatar, ordered buttons and click tracking through your own short links. Plus the list of what's missing.
Routing forms in Cal: send each lead to the right meeting
A few questions before the calendar, and each visitor lands on the right event type. How to build routing forms in Cal, how rules are evaluated and where the limits are.
Why we chose AGPLv3 over MIT, Apache or BSL
What AGPLv3 requires, what it doesn't, the network clause in plain words, and what it means if your company self-hosts zerosoft.
Self-hosting zerosoft with Docker, step by step
From a blank VPS to a running zerosoft with HTTPS, Google login, backups, updates and the cron job people forget. Every command.
Running two-week cycles in Track: a playbook for small teams
How a small team runs cycles in Track with issues, sub-issues, relations, estimates, custom statuses and four views, plus what it still lacks.
Moving contacts from HubSpot to zerosoft CRM with a CSV
Export contacts and companies from HubSpot and import them into zerosoft CRM: column mapping, dedupe by email and domain, and what doesn't come along.
Custom domains for short links: DNS, step by step
How to serve Link short URLs from go.yourcompany.com: which DNS record to create, how verification works on zerosoft Cloud and on your own server, and what usually goes wrong.
Round-robin scheduling in Cal: one link for the whole team
Share one booking link across a sales or support team, and see exactly how Cal picks the host for each meeting: cursor, pool order and conflicts.
What comes after the subscription: four business models
The subscription solved two problems that mostly went away. Four models that can replace it, and why we picked the least exciting one.
How zerosoft Cloud is priced
The software is AGPLv3 and costs $0 to self-host. The cloud has a free tier and then charges per workspace for usage. The details, and the questions people ask.
Self-hosting in 2026: a $5 VPS and three commands
Containers, managed DNS and SQLite made self-hosting a small job. What it takes today, and when it still isn't worth it.
What it costs to run a link shortener: the full math
Bitly charges $35 a month. We priced redirects, analytics and storage on Link's real architecture. It comes to cents.
How software went from a one-time purchase to a monthly rent
You used to buy a box and keep the software. Now most work tools are rented with no end date. How that happened, and what's changing.
Free of charge vs free to use: why the license matters more than the price
A free plan is a price the vendor can change. An open source license is a set of rights you keep. What that difference means for the tools your company runs on.
What's inside a $30-per-user project tool
A project tool is a database, a drag-and-drop interface and a login. We list each part, what it costs to run, and where the rest of the price comes from.
The zerosoft manifesto: what work software costs to run, and what we charge
Moving cards, storing contacts and shortening links cost cents to run. We publish the code under AGPLv3 and charge for usage, not for seats.
Bitly Core costs $35 a month. Here's what the redirects cost to serve.
We go through Bitly's paid plan item by item and put each one next to the infrastructure it needs. The difference is margin, not engineering.
How Link is built: Next.js, SQLite and one route handler
The redirect is a route handler that answers in milliseconds, backed by SQLite and nothing else. The whole architecture, on one page.
Link analytics without cookies: what one HTTP request tells us
Link counts clicks with no cookies, no JavaScript and no fingerprinting. Everything comes from the request the browser already sends.
QR codes are an open standard. Link includes them.
QR has been an open standard since 1994 (ISO/IEC 18004), with patents waived by its inventor. Generating one costs nothing, so Link makes one for every link.
What we took from Linear for Track, and what Linear's per-seat price adds up to
Linear is a great issue tracker: fast, keyboard-driven, built around cycles. Its price grows with every hire. Why we built Track, and what it does and doesn't do yet.
HubSpot prices grow with your contact list. A contact is a few bytes.
HubSpot charges more as your database grows, but storing a contact costs almost nothing. What your contacts cost to keep, and how to take them with you.
Calendly at $12 per user: what a booking costs to serve
A scheduling tool is a public availability page and a form that writes to your calendar. What Calendly charges for it, what a booking costs to run, and what Cal does instead.
Lock-in is how SaaS keeps customers
Partial exports, proprietary formats, fragile integrations and prices that grow with you. Four tactics that raise the cost of leaving, and how to check for them.
How to test a SaaS export before you sign up
Most exports leave things behind. What a complete export should include, a test you can run in ten minutes, and how zerosoft handles it.
Why sign-in is Google only
Passwords are the weakest part of most logins, so we delegated sign-in to Google. The reasons, and the trade-offs.
SQLite is enough for apps like ours
The most deployed database runs in your phone, your browser and Link. Millions of rows, WAL mode, and backups that are a file copy.
What the cloud costs, from public price lists
A VPS costs $5. A GB of storage costs cents. Bandwidth is sold by the terabyte. All of it is public, and almost nobody adds it up.
Work software is becoming a commodity, like electricity did
Factories once ran their own generators. Then the grid came and power was priced at cost. Work software is on the same path, and users come out ahead.
How to contribute to zerosoft: issues, pull requests and translations
The code and the roadmap are public, and the blog ships in three languages. Where to start: bug reports, pull requests, translations, docs and product ideas.
Our public roadmap: how we decided what came after Link
We published the roadmap with quarters and criteria. What we planned after Link, how we chose the order, and where to follow it now.
Why our site is mostly zeros
No stock photos, no gradients, one large zero made of zeros. The design follows the same rule as the pricing: nothing we don't need.
Per-seat pricing charges you for growing
Every hire makes your tools more expensive, even though an extra user costs the vendor almost nothing. What per-seat pricing does to teams, and what we charge for instead.
What zerosoft collects, and what it doesn't
Link stores the country, referrer and device of a click, never the IP address or a cookie. What we record, what we leave out, and why.
Rebuilding a SaaS product in a week: how we built Link
A Bitly-class shortener used to be a six-month project for a team. We built Link in about a week with AI tools. What that week covered, and what it means for prices.
Open source runs the servers. The apps on top are still rented.
Linux, Postgres, nginx and Kubernetes already run the internet. The tools office workers use every day are the part that stayed closed. That's the layer we're building.
Why every endpoint of the v1 API is documented
The public v1 API is documented endpoint by endpoint at /docs. A documented API is how you check that leaving is possible.
If work software cost what it costs to run: a thought experiment
Imagine every work tool is open source and the hosted version is billed by usage. What happens to IT budgets, to vendors and to where innovation goes.