Small Business Stack: My Non-Generic Productivity Workflow
The "No-Bloat" Operational Stack
The goal here isn't to have the most features, but the shortest path from "idea" to "done." Here is the specific configuration I use to keep a small business running without losing my mind to notification fatigue.
1. Tana for Knowledge Graphing
Instead of a linear folder system (like Notion or Evernote), I use Tana because it treats everything as a "node." For a business owner, this is critical because a single entity—like a Client—is simultaneously a lead, a project, a billing entity, and a source of feedback.
In Tana, I use "Supertags" to handle this. For example, when I tag a node as #client, it automatically pulls in fields for LTV, Contact Email, and Next Milestone. This prevents the "where did I put that note?" scramble.
2. Linear for Execution
I switched to Linear because it's built for speed. Most tools are designed for managers to watch people work; Linear is designed for people who actually do the work. The keyboard-centric navigation is a massive efficiency gain.
My specific setup for task triage:
- Cycle: I use 1-week cycles. If it's not in the current cycle, it doesn't exist in my head.
- Triage: Everything lands in the Triage bucket first. I spend 10 minutes every morning moving things to "Todo" or archiving them.
3. Raycast for System-Wide Automation
Raycast has completely replaced Spotlight and several small utility apps. The real value here is the Store and the ability to write custom scripts. Instead of opening a browser, logging into a dashboard, and searching for a client's ID, I use a custom script to fetch data via API directly into the search bar.
If you want to automate a repetitive task, you can write a simple script in TypeScript. Here is a basic example of how I structure a script to quickly log a time-entry to my tracking system:
import { showToast, form } from "@raycast/api";
export default async function Command() {
const { project, duration } = await form.createForm({
as hundredPercent: true,
fields: [
{ name: "project", type: "text", placeholder: "Project Name" },
{ name: "duration", type: "text", placeholder: "Hours (e.g. 1.5)" },
],
});
// Logic to send this to a webhook or database
await fetch("https://your-api-endpoint.com/log", {
method: "POST",
body: JSON.stringify({ project, duration, date: new Date().toISOString() }),
});
await showToast({ style: "success", title: "Time Logged" });
}4. Readwise Reader for Information Processing
The "read it later" trap is real. I use Reader not just to save articles, but to pipe highlights directly into Tana. This creates a closed-loop AI workflow: I find a technical insight → highlight in Reader → it appears in my Tana graph → I use it in a client deliverable.
5. Claude Code for Rapid Prototyping
As a non-technical founder who can code a bit, Claude Code (the CLI tool) has changed how I handle internal tooling. I no longer spend hours debugging a simple Python script for data cleanup. I run the agent directly in my terminal, give it the error log, and let it apply the fix.
Real-world fix example:
When my CSV export script was failing due to encoding issues with UTF-8 BOM, I didn't go to StackOverflow. I ran:claude "Fix the encoding error in export.py and ensure it handles special characters for the client report"
It identified the utf-8-sig requirement in Python's open() function and patched it in seconds.
Is this stack worth it?
If you are a solo founder or a team of under five, the "industry standard" tools are often too heavy. The transition to a graph-based knowledge system (Tana) and a speed-focused execution tool (Linear) removes the friction of "managing the tool" and lets you focus on the actual business.
The biggest hurdle is the learning curve—Tana and Raycast require a mindset shift—but the ROI in reclaimed time is measurable. I've cut my "admin time" by roughly 4 hours a week just by eliminating the context switching between five different browser tabs.
