<?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>TextCortex &#8211; iAIFeed</title>
	<atom:link href="https://www.iaifeed.com/tag/textcortex/feed" rel="self" type="application/rss+xml" />
	<link>https://www.iaifeed.com</link>
	<description>iAIFeed</description>
	<lastBuildDate>Wed, 18 Nov 2026 12:43:49 +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>TextCortex &#8211; iAIFeed</title>
	<link>https://www.iaifeed.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>How to Build a Cold Email Workflow With TextCortex</title>
		<link>https://www.iaifeed.com/how-to-build-a-cold-email-workflow-with-textcortex</link>
					<comments>https://www.iaifeed.com/how-to-build-a-cold-email-workflow-with-textcortex#respond</comments>
		
		<dc:creator><![CDATA[iamltlb]]></dc:creator>
		<pubDate>Wed, 18 Nov 2026 12:43:49 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[TextCortex]]></category>
		<guid isPermaLink="false">https://www.iaifeed.com/how-to-build-a-cold-email-workflow-with-textcortex</guid>

					<description><![CDATA[A repeatable TextCortex outreach workflow: separate knowledge bases per audience, personas, Gmail and LinkedIn rewrites, and where the tool breaks at team scale.]]></description>
										<content:encoded><![CDATA[<p><a href="https://www.iaifeed.com/ai-tool/textcortex">TextCortex</a>&#8216;s real advantage at the $20 tier is not the writing panel — it is running the same rewrite across Gmail, LinkedIn, HubSpot and Notion without ever leaving the tab. Here is how to build a repeatable outreach workflow with it, plus what breaks at scale.</p>
<h2 id="how-do-you-set-up-a-cold-email-workflow-in-textcortex">How do you set up a cold email workflow in TextCortex?</h2>
<p>The goal is boring consistency: every rep writes in the same voice, with the same proof points, without a manager reviewing drafts.</p>
<ol>
<li><strong>Build one knowledge base per audience.</strong> Not one for the whole company. A &#8220;logistics ops managers&#8221; base and a &#8220;SaaS founders&#8221; base retrieve very different fragments, and mixing them produces mush.</li>
<li><strong>Seed it with evidence, not adjectives.</strong> Ten winning emails, three case study summaries with numbers, one objection-handling doc. Skip your brand guidelines; the tool copies sentence patterns more than tone rules.</li>
<li><strong>Create a persona.</strong> Personas are saved prompt presets — role, audience, tone, output length. A sales persona might read &#8220;SDR writing to operations director, 80 words max, one specific metric, no exclamation marks.&#8221;</li>
<li><strong>Test in the extension, not the web app.</strong> Gmail&#8217;s DOM is different from a plain textarea, and formatting disappears in ways the web app will not show you.</li>
</ol>
<p>Run the same prompt ten times fresh. If the outputs are near-identical, your seed documents are too short and the model is defaulting. Add variation.</p>
<h2 id="does-the-gmail-and-linkedin-integration-actually-save-time">Does the Gmail and LinkedIn integration actually save time?</h2>
<p>Yes, when the task is rewriting text that already exists. Copy-paste into ChatGPT and back is about six seconds per edit; the inline bubble is about one. Over sixty emails that is five minutes, not nothing, but not the main win.</p>
<p>The real gain is not breaking flow. Attention cost matters more than keystroke cost for repetitive writing.</p>
<p>What does not work well: composing from scratch inside Gmail. The writing panel is narrow, and long drafts scroll badly. Write the body in Notion or Docs, then use the extension to tighten the last paragraph and rewrite the subject line.</p>
<p><strong>A concrete number worth knowing:</strong> reply-rate copy usually improves with a shorter ask. Ask TextCortex for a version with the CTA reduced to one sentence and compare. In practice that rewrite is where most of the value sits, not in generating new paragraphs.</p>
<h2 id="how-does-it-handle-compliance-and-data">How does it handle compliance and data?</h2>
<p>The company says data is processed on EU infrastructure and offers a GDPR DPA on paid plans. Uploaded knowledge base files are stored per-account; there is no documented retention window beyond the standard policy.</p>
<p>Practical rules if you handle regulated industries:<br />
Do not upload customer lists with PII into a knowledge base. The retrieval layer will happily paste a real name into a draft.<br />
Disable sync on shared machines; the extension caches your last prompts locally.<br />
On the Team plan, knowledge bases are shareable, so decide who can edit them before you seed them with any internal pricing.</p>
<h2 id="how-does-textcortex-compare-with-a-plain-chatgpt-workflow">How does TextCortex compare with a plain ChatGPT workflow?</h2>
<table>
<thead>
<tr>
<th>Capability</th>
<th>TextCortex Pro</th>
<th>ChatGPT Plus + manual copy</th>
</tr>
</thead>
<tbody>
<tr>
<td>Price</td>
<td>~$20/month yearly</td>
<td>$20/month</td>
</tr>
<tr>
<td>Works inside Gmail/LinkedIn</td>
<td>Yes, inline</td>
<td>No</td>
</tr>
<tr>
<td>Saved brand context</td>
<td>Knowledge base + personas</td>
<td>Custom GPTs or project files</td>
</tr>
<tr>
<td>Multi-step reasoning</td>
<td>Weak</td>
<td>Strong</td>
</tr>
<tr>
<td>Code and data analysis</td>
<td>Not offered</td>
<td>Yes</td>
</tr>
<tr>
<td>Output length ceiling</td>
<td>Short by design</td>
<td>Long</td>
</tr>
</tbody>
</table>
<p>The honest read: TextCortex wins on speed for short, repetitive, in-app writing. It loses badly on anything that needs reasoning — contract analysis, multi-step research, spreadsheet work. Some teams pay for both and that is not wasteful.</p>
<h2 id="what-are-the-real-limitations-at-team-scale">What are the real limitations at team scale?</h2>
<ul>
<li><strong>No API worth building on.</strong> — There is an enterprise API but no public docs with stable rate limits, so automation is off the table for most.</li>
<li><strong>Snippet caps scale awkwardly.</strong> — Pro is &#8220;unlimited&#8221; subject to fair use; a five-person team on individual Pro accounts will hit soft limits during a campaign push and get throttled instead of billed.</li>
<li><strong>No version history across browsers.</strong> — Edit the same draft in Chrome at home and the desktop app at work and you can end up with two diverging copies.</li>
<li><strong>Personas do not share between seats</strong> — on individual plans, so every rep builds their own. On Team, they do.</li>
<li><strong>Language quality drops for non-English.</strong> — German and French are decent; Portuguese and Japanese output needed heavy editing in testing.</li>
</ul>
<h2 id="who-should-standardize-on-it">Who should standardize on it?</h2>
<p>Outbound teams of 3-15 people who write in the browser all day and want consistent voice without a content ops person. Also good for solo founders doing LinkedIn-plus-email outreach on a budget.</p>
<p>Not the right fit for: content teams producing 2,000-word articles, anyone needing API automation, or teams whose main writing surface is Google Docs on Firefox.</p>
<h2 id="quick-summary">Quick Summary</h2>
<ul>
<li>Build one knowledge base per audience, not per company — mixed bases produce generic drafts.</li>
<li>The extension&#8217;s advantage is staying inside Gmail/LinkedIn, not generating long copy.</li>
<li>Pro at about $20/month yearly is where unlimited generations and five knowledge bases start.</li>
<li>No usable public API; snippet limits are enforced by throttling, not overage billing.</li>
<li>Strong for outbound and short marketing copy; weak for research, code, and long-form.</li>
</ul>
]]></content:encoded>
					
					<wfw:commentRss>https://www.iaifeed.com/how-to-build-a-cold-email-workflow-with-textcortex/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>How to Install TextCortex and Use Its Knowledge Base</title>
		<link>https://www.iaifeed.com/how-to-install-textcortex-and-use-its-knowledge-base</link>
					<comments>https://www.iaifeed.com/how-to-install-textcortex-and-use-its-knowledge-base#respond</comments>
		
		<dc:creator><![CDATA[iamltlb]]></dc:creator>
		<pubDate>Wed, 18 Nov 2026 12:43:01 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[TextCortex]]></category>
		<guid isPermaLink="false">https://www.iaifeed.com/how-to-install-textcortex-and-use-its-knowledge-base</guid>

					<description><![CDATA[TextCortex is a browser-based AI writing assistant with a 20-snippet free tier. Learn the install steps, how the knowledge base shapes drafts, and 2026 pricing.]]></description>
										<content:encoded><![CDATA[<p>TextCortex is an AI writing assistant that runs as a browser extension, a Chrome sidebar, and a desktop app, with a free plan of 20 daily knowledge snippets. You select text anywhere, pick a rewrite action, and the replacement lands in the field you were already typing in.</p>
<h2 id="what-is-textcortex">What is TextCortex?</h2>
<p><a href="https://www.iaifeed.com/ai-tool/textcortex">TextCortex</a> is a Berlin-based AI writing tool launched in 2021 by Nikolai Filonowitsch and David Lukić. It started as a browser extension for people writing sales emails in Gmail and moved into a broader platform with a knowledge base, custom &#8220;personas,&#8221; and a Chrome sidebar that can read the page you are on.</p>
<p>The pitch has always been the same: meet writers inside whatever text box they already use, instead of making them open a separate chat window.</p>
<p>Its free tier is one of the more usable ones in this category. You get 20 &#8220;knowledge snippets&#8221; a day, which the company counts as text generations against your saved knowledge base, plus unlimited basic rewrite actions in some contexts. The catch is that free accounts cannot add custom knowledge, so the clever personalization features sit behind the paywall.</p>
<h2 id="how-do-you-install-and-set-up-textcortex">How do you install and set up TextCortex?</h2>
<p>The setup is quick and slightly fiddly in one specific spot.</p>
<ol>
<li>Install the Chrome or Edge extension from the store, or grab the desktop app if you work in Word, Notion desktop, or VS Code.</li>
<li>Create an account with Google or email. No credit card for the free tier.</li>
<li>Pin the extension icon — it hides in the puzzle-piece menu by default and half the complaints online are from people who installed it and then could not find it.</li>
<li>On a page like Gmail or LinkedIn, click into a text field. A small TextCortex bubble appears at the edge of the field.</li>
<li>Select text and hit the bubble, or press the shortcut (Ctrl+Space by default) to open the writing panel.</li>
</ol>
<p>On free plans, the knowledge base feature shows an upgrade prompt instead of a file upload box. Do not spend twenty minutes looking for the button; it is not there.</p>
<h2 id="how-does-the-knowledge-base-change-the-output">How does the knowledge base change the output?</h2>
<p>This is the part that separates TextCortex from a generic rewriter. You upload documents — past emails, product specs, your company tone guide, a list of objections customers raise — and the tool retrieves from them when generating.</p>
<p>A practical example. Upload twelve of your best-performing cold emails. Then ask for a new opener for a prospect in logistics. Instead of generic &#8220;I hope this email finds you well,&#8221; you get something patterned after your own voice, referencing specifics from your library.</p>
<p>The retrieval is not a full RAG system with citations. It surfaces fragments and you get a plausible-sounding draft, not a sourced answer. For copywriting that is fine. For anything factual, verify before sending.</p>
<h2 id="what-does-textcortex-cost-in-2026">What does TextCortex cost in 2026?</h2>
<table>
<thead>
<tr>
<th>Plan</th>
<th>Price</th>
<th>What you get</th>
</tr>
</thead>
<tbody>
<tr>
<td>Free</td>
<td>$0</td>
<td>20 knowledge snippets/day, limited templates</td>
</tr>
<tr>
<td>Starter</td>
<td>About $9.99/month yearly</td>
<td>100 snippets/month, 1 knowledge base</td>
</tr>
<tr>
<td>Pro</td>
<td>About $19.99/month yearly</td>
<td>Unlimited snippets, 5 knowledge bases, all integrations</td>
</tr>
<tr>
<td>Team</td>
<td>Custom</td>
<td>Shared knowledge, seats, admin</td>
</tr>
</tbody>
</table>
<p>The jump from Starter to Pro is where most individual users land, mostly because 100 snippets a month disappears in a week of real writing.</p>
<h2 id="where-does-it-fall-short">Where does it fall short?</h2>
<ul>
<li><strong>Snippet math is confusing.</strong> The company counts generations, not words, and the definition changes between the extension and the web app. Budget conservatively.</li>
<li><strong>No long-form editor worth using.</strong> The web app&#8217;s document view is basic; people use it as a sidecar in Google Docs or Notion, not as a primary writing surface.</li>
<li><strong>Firefox and Safari support is behind.</strong> Chrome-first is accurate. If your team is on Safari, you will be waiting.</li>
<li><strong>Rewrite quality plateaus.</strong> For short marketing copy it is competitive. For technical writing it tends to flatten specifics into generic claims.</li>
<li><strong>Output can drift into marketing register</strong> even when you ask for neutral tone, so editing is not optional.</li>
</ul>
<h2 id="who-is-it-for">Who is it for?</h2>
<p>Use <a href="https://www.iaifeed.com/ai-tool/textcortex">TextCortex</a> if you write sales emails, LinkedIn posts, product descriptions, or support replies inside web apps all day, and you want rewrites without copying text into ChatGPT and back. Small marketing teams benefit most from the shared knowledge base.</p>
<p>Skip it if you are writing long technical documents, need citation-backed research, or work primarily in Firefox/Safari. In those cases a chat-based assistant plus a good text expander covers the same ground for less.</p>
<h2 id="quick-summary">Quick Summary</h2>
<ul>
<li>TextCortex is a Berlin-built AI writing assistant (2021) that lives as a browser extension and desktop app.</li>
<li>Free tier gives 20 knowledge snippets a day; Pro at about $20/month yearly unlocks unlimited generations.</li>
<li>The knowledge base lets you condition output on your own past emails and docs, but it is retrieval-flavored, not citation-grade.</li>
<li>Chrome/Edge first — Firefox and Safari support lags.</li>
<li>Best for outreach and marketing copy inside web apps; weak for long technical writing.</li>
</ul>
]]></content:encoded>
					
					<wfw:commentRss>https://www.iaifeed.com/how-to-install-textcortex-and-use-its-knowledge-base/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
