<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <id>blog</id>
    <title>with-tap.ai — Blog</title>
    <updated>2026-11-05T04:49:46.142Z</updated>
    <generator>https://github.com/jpmonette/feed</generator>
    <link rel="alternate" href="https://with-tap.ai/"/>
    <subtitle>Composable tools, built in public. Follow what we replace and how we run it.</subtitle>
    <entry>
        <title type="html"><![CDATA[Building With TAP in public]]></title>
        <id>/blog/building-with-tap</id>
        <link href="https://with-tap.ai/blog/building-with-tap"/>
        <updated>2026-10-27T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[Why we're bringing our tools together, and what we'll show as we build.]]></summary>
        <content type="html"><![CDATA[<!--$--><h1 class="rp-toc-include" id="building-with-tap-in-public"><a href="#building-with-tap-in-public" class="rp-header-anchor rp-link" aria-hidden="true" tabindex="-1">#</a>Building With TAP in public<!-- --> </h1>
<p>We want tools we can change, connect, and use with agents. That&#x27;s the reason for With TAP.</p>
<p>We&#x27;re bringing our calendar, email, CRM, design, forms, social, and live work into a composable suite. Revenue Engine is the pack that brings Calendar, Email, CRM, and Social together with the revenue workflows around them.</p>
<p>This repository starts with the public site and the holding app. Existing tools will move over in stages. A new repository isn&#x27;t a product launch, and a planned subdomain isn&#x27;t evidence that a tool is ready.</p>
<p>We&#x27;ll use this blog for the longer decisions and <a href="/log/index.html" class="rp-link">the build log</a> for dated changes. When we say we replaced something, we&#x27;ll show the replacement and its limits.</p><!--/$-->]]></content>
        <author>
            <name>With TAP team</name>
        </author>
    </entry>
</feed>