The Bisonflow blog
Notes from building.
Software, design, and the work around shipping a product. Essays by Anthony Abramo, the developer building Bisonflow.
11 articles
Design / Building Bisonflow
Redesigning Bisonflow around the work you came to do
Why the new workspace gives more room to issues, timelines, and documents, and what changed when I treated mobile as a different working context.
Founder notes / Product
A free way in, and clearer reasons to pay
The thinking behind Bisonflow’s proposed Free, Basic, Business, and Enterprise offer. A product direction, with no change to current subscriptions yet.
Engineering / AI
Your coding assistant should not need a pasted copy of the backlog
Development preview: OAuth connections, six scoped MCP tools, and the server checks that keep external assistants inside your workspace permissions.
Product / AI
The Agent beta should earn your trust one change at a time
How to try Bisonflow’s project Agent, what reviewed commands are for, and the mistakes I want the beta to expose before it gets more responsibility.
Engineering / Building Bisonflow
Why I moved Bisonflow from Next.js to TanStack Start
The reasoning behind Bisonflow’s framework migration, the boundaries I kept, and the unglamorous work that mattered more than changing route files.
Engineering / AI
Before AI updates the project, it needs to know which project
A concrete standard for AI in project software: inspect the right evidence, admit missing context, and make proposed changes reviewable.
Product / AI
A useful voice command ends with something you can inspect
Where voice helps during project work, where typing wins, and why the visible result matters more than a perfect transcription.
Practice / Releases
Write the release note before Friday evening
A practical way to keep release scope and evidence together, so shipping does not end with an archaeological dig through completed tickets.
Practice / Planning
Your roadmap can change without becoming fiction
How to review a slipping plan, separate dates from assumptions, and make a useful decision before the release is already late.
Practice / Product
The expensive part of switching tabs is remembering why
A task can be perfectly up to date and still leave its reader guessing. Here is how I keep decisions useful after the conversation ends.
Founder notes / Product
I wanted to build software, not keep explaining the project
Why I'm building Bisonflow for people who write the code, make the product calls, and still have to remember why the plan changed.
Your next move
See your next project clearly.
The best way to understand Bisonflow is to use it.