<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>heptabase &#8211; iAIFeed</title>
	<atom:link href="https://www.iaifeed.com/tag/heptabase/feed" rel="self" type="application/rss+xml" />
	<link>https://www.iaifeed.com</link>
	<description>iAIFeed</description>
	<lastBuildDate>Sat, 14 Nov 2026 12:44:01 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.5</generator>

<image>
	<url>https://www.iaifeed.com/wp-content/uploads/2026/07/cropped-iaifeed1-80x80.png</url>
	<title>heptabase &#8211; iAIFeed</title>
	<link>https://www.iaifeed.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>How to Turn Meeting Notes into a Heptabase Knowledge Base</title>
		<link>https://www.iaifeed.com/how-to-build-a-heptabase-knowledge-base-from-meeting-notes</link>
					<comments>https://www.iaifeed.com/how-to-build-a-heptabase-knowledge-base-from-meeting-notes#respond</comments>
		
		<dc:creator><![CDATA[iamltlb]]></dc:creator>
		<pubDate>Sat, 14 Nov 2026 12:44:01 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[heptabase]]></category>
		<guid isPermaLink="false">https://www.iaifeed.com/how-to-build-a-heptabase-knowledge-base-from-meeting-notes</guid>

					<description><![CDATA[Dumping every meeting into whiteboards produces chaos by month three. Here is the card format and board structure that keeps a Heptabase base useful a year later.]]></description>
										<content:encoded><![CDATA[<p>A <a href="https://www.iaifeed.com/ai-tool/heptabase">Heptabase</a> knowledge base built from meeting notes fails for one reason: the notes are written for the meeting, not for retrieval. Someone searches six months later for why a decision was made and finds three paragraphs about who was on the call.</p>
<p>Heptabase handles this better than a folder system, because you can separate the decision from the discussion physically. The format below keeps a board useful after 100 meetings.</p>
<h2 id="what-should-one-meeting-note-look-like">What should one meeting note look like?</h2>
<p>One card per decision, not one card per meeting. A 45-minute call usually produces two to four decisions and a pile of noise.</p>
<p>Card template that works:</p>
<ul>
<li><strong>Title</strong>: a decision, phrased as a sentence. &#8220;Billing moves to Stripe in Q1&#8221; not &#8220;Billing sync 11/12&#8221;.</li>
<li><strong>Body</strong>: two sentences of context, one line of the owner, one line of the deadline.</li>
<li><strong>Source</strong>: the link to the full meeting notes, stored separately.</li>
</ul>
<p>Heptabase cards are meant to be atomic. If a card needs sub-headings, it is holding too much.</p>
<h2 id="how-do-you-structure-the-board">How do you structure the board?</h2>
<p>Three zones, arranged left to right.</p>
<ol>
<li><strong>Inbox</strong> — new cards land here after every meeting. Nothing gets organised during the call.</li>
<li><strong>Projects</strong> — cards grouped by active workstream. Each group gets a Section with the project name.</li>
<li><strong>Decisions</strong> — a chronological column of decisions that cut across projects: pricing changes, hiring, tooling.</li>
</ol>
<p>Once a week, spend 15 minutes moving inbox cards into their zones. That is the entire maintenance cost.</p>
<h2 id="how-do-you-connect-decisions-to-projects">How do you connect decisions to projects?</h2>
<p>Use links, not duplicate cards. If a pricing decision affects two projects, drop the card in Decisions and add a linked card reference in each project zone.</p>
<p>Duplicating creates two versions that drift. Linking keeps one source of truth and shows up visually when you hover the connection.</p>
<h2 id="what-does-the-ai-chat-add-here">What does the AI chat add here?</h2>
<p>Attach the Decisions column and ask questions that would otherwise take ten minutes of scrolling: &#8220;what did we decide about vendor X and when?&#8221; or &#8220;which projects are blocked on the design system?&#8221;</p>
<p>The chat answers from attached cards, so accuracy equals card quality. If your cards say &#8220;discussed pricing&#8221;, the answer is useless. If they say &#8220;moved Pro tier to $19, effective March 1, owner Dana&#8221;, it is precise.</p>
<h2 id="what-breaks-this-system">What breaks this system?</h2>
<p>Two things, both common.</p>
<p><strong>Too many inbox cards.</strong> If you never do the weekly 15 minutes, the inbox becomes the folder system you were escaping. Set a recurring reminder.</p>
<p><strong>Cards without owners.</strong> A decision card without a named owner is a discussion, not a decision. Skip those cards entirely; the full meeting notes still exist if someone needs them.</p>
<p>A third failure is board sprawl. If you have 15 whiteboards after six months, you have no system. Cap it at three: current quarter, archive, and one sandbox.</p>
<h2 id="who-should-not-copy-this-setup">Who should not copy this setup?</h2>
<p>Teams that need shared notes. Heptabase is a single-user tool, so this works for an individual building their own memory, not for a team wiki.</p>
<p>Anyone who never rereads notes. If you have never once searched for an old meeting, this is elaborate filing for nothing.</p>
<h2 id="quick-summary">Quick Summary</h2>
<ul>
<li>Write one card per decision, titled as a sentence, with owner and deadline on separate lines.</li>
<li>Keep three board zones: Inbox, Projects, and a cross-cutting Decisions column.</li>
<li>Spend 15 minutes a week moving inbox cards; that is the whole maintenance load.</li>
<li>Link cards across zones instead of duplicating, so there is one source of truth.</li>
<li>Cap yourself at three whiteboards total or the system stops being a system.</li>
</ul>
]]></content:encoded>
					
					<wfw:commentRss>https://www.iaifeed.com/how-to-build-a-heptabase-knowledge-base-from-meeting-notes/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>How to Run a Literature Review in Heptabase Whiteboards</title>
		<link>https://www.iaifeed.com/how-to-run-a-literature-review-in-heptabase-whiteboards</link>
					<comments>https://www.iaifeed.com/how-to-run-a-literature-review-in-heptabase-whiteboards#respond</comments>
		
		<dc:creator><![CDATA[iamltlb]]></dc:creator>
		<pubDate>Sat, 14 Nov 2026 12:43:43 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[heptabase]]></category>
		<guid isPermaLink="false">https://www.iaifeed.com/how-to-run-a-literature-review-in-heptabase-whiteboards</guid>

					<description><![CDATA[Heptabase whiteboards replace nested folders with spatial cards. Here is how to set up a research project, link sources, and use the AI chat without generating slop.]]></description>
										<content:encoded><![CDATA[<p><a href="https://www.iaifeed.com/ai-tool/heptabase">Heptabase</a> is a visual note-taking tool built around an infinite whiteboard. Instead of stacking notes in folders, you write atomic cards and arrange them in space. For research work, that turns a mountain of PDFs into a map you can read at a glance.</p>
<p>The tool ships with a split-screen PDF reader and a context-aware AI chat, so the workflow runs from reading to synthesis without leaving the app. Below is a setup that survives a long project.</p>
<h2 id="what-makes-heptabase-different-from-notion-or-obsidian">What makes Heptabase different from Notion or Obsidian?</h2>
<p>Spatial arrangement. Notion is a database with pages, Obsidian is a graph of linked files. Heptabase is a canvas where position carries meaning.</p>
<p>That sounds cosmetic until you have 200 notes. In a folder system, you sort by tag and hope. On a whiteboard, you physically group &#8220;methods&#8221; in one corner, &#8220;open questions&#8221; in another, and the structure is visible without opening anything.</p>
<h2 id="how-do-you-start-a-research-project">How do you start a research project?</h2>
<p>One whiteboard per project, named with a date so you can archive it later.</p>
<ol>
<li>Create the whiteboard, then add three sections with the Section tool: Sources, Claims, Questions.</li>
<li>Drop every PDF into the Sources section. Heptabase imports them into the built-in reader.</li>
<li>Highlight inside the reader, and each highlight becomes a card you can drag onto the canvas.</li>
<li>File each highlight card under Claims or Questions, depending on what it does.</li>
</ol>
<p>Do not try to be tidy in the first week. The point of the board is to dump, then arrange.</p>
<h2 id="how-do-you-handle-pdfs-and-highlights">How do you handle PDFs and highlights?</h2>
<p>The split-screen reader is the feature that makes the workflow viable. You read on one side, and pulled quotes land on the other as cards.</p>
<p>Two habits help:</p>
<ul>
<li><strong>Highlight sparingly.</strong> Ten highlights per paper, maximum. If everything is highlighted, nothing is.</li>
<li><strong>Rewrite in your own words on the card.</strong> Heptabase keeps the source link, so you do not lose the quote, but your note should be your sentence. Future you reads the note, not the paper.</li>
</ul>
<h2 id="how-should-you-use-the-ai-chat">How should you use the AI chat?</h2>
<p>Attach the whiteboard or specific cards to the chat, then ask it to summarise or find gaps. The key is context selection.</p>
<p>Good prompts:</p>
<ul>
<li>&#8220;These twelve cards describe competing methods. Group them into three families and name the axis they differ on.&#8221;</li>
<li>&#8220;Which of these claims contradict each other, and on what specific number?&#8221;</li>
</ul>
<p>Bad prompts: &#8220;summarise my research.&#8221; Attaching the whole board produces a generic summary that reads well and says nothing. Attach 10 to 20 cards, not 200.</p>
<p>The AI only sees what you attach, and it grounds answers in your cards rather than inventing citations. That is the difference between this and asking a chatbot about a topic it half-remembers.</p>
<h2 id="what-does-it-cost-and-where-does-it-hit-limits">What does it cost and where does it hit limits?</h2>
<p>The paid plan is around $8.99 per month billed annually, and the free tier is limited enough that serious projects outgrow it within a month.</p>
<p>Limits worth knowing:</p>
<ul>
<li>Whiteboards get slow past roughly 300 to 400 visible cards. Split into sub-boards once you cross that.</li>
<li>No native mobile editing of whiteboards; the mobile app is mostly a reader.</li>
<li>Collaboration is limited. It is a single-user tool with light sharing, not a multiplayer doc.</li>
</ul>
<h2 id="who-is-this-workflow-wrong-for">Who is this workflow wrong for?</h2>
<p>Teams. If three people need to edit the same research, use Notion, Google Docs, or a proper reference manager.</p>
<p>People who think linearly. If your writing process is &#8220;outline, then fill in&#8221;, the canvas adds friction. Heptabase rewards people who think in fragments and connect later.</p>
<h2 id="quick-summary">Quick Summary</h2>
<ul>
<li>Heptabase is a whiteboard-first note tool: atomic cards arranged in space, plus a split-screen PDF reader.</li>
<li>Start with three sections (Sources, Claims, Questions) and dump first, arrange later.</li>
<li>Highlight ten quotes per paper at most, and rewrite each on the card in your own words.</li>
<li>Attach 10 to 20 cards to the AI chat, never the whole board, or summaries go generic.</li>
<li>Around $8.99 per month annually; boards slow past 300 to 400 visible cards; not built for team editing.</li>
</ul>
]]></content:encoded>
					
					<wfw:commentRss>https://www.iaifeed.com/how-to-run-a-literature-review-in-heptabase-whiteboards/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
