<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[aibrevo engineering notes]]></title><description><![CDATA[aibrevo engineering notes]]></description><link>https://aibrevo-notes.hashnode.dev</link><image><url>https://cdn.hashnode.com/uploads/logos/6afeb832981d08b9146c1393/f7158748-9230-4c62-9d05-645dd5ce53b0.png</url><title>aibrevo engineering notes</title><link>https://aibrevo-notes.hashnode.dev</link></image><generator>RSS for Node</generator><lastBuildDate>Fri, 20 Nov 2026 19:56:40 GMT</lastBuildDate><atom:link href="https://aibrevo-notes.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[What goes into an MVP? We coded 43 first versions]]></title><description><![CDATA[Founders ask what to put in an MVP. Our answer was always a vague "the smallest thing that does the job", which is not an answer. So we went back through…]]></description><link>https://aibrevo-notes.hashnode.dev/what-goes-into-an-mvp-we-coded-43-first-versions</link><guid isPermaLink="true">https://aibrevo-notes.hashnode.dev/what-goes-into-an-mvp-we-coded-43-first-versions</guid><category><![CDATA[mvp]]></category><category><![CDATA[startup]]></category><category><![CDATA[Web Development]]></category><dc:creator><![CDATA[aibrevo]]></dc:creator><pubDate>Thu, 19 Nov 2026 08:55:40 GMT</pubDate><content:encoded><![CDATA[<p>Founders ask what to put in an MVP. Our answer was always a vague "the smallest thing that does the job", which is not an answer. So we went back through 43 first versions our team shipped and wrote down what each one actually contained.</p>
<p>We sorted the headline features of each build into 19 building blocks, such as payments, search, notifications, a dashboard for the people running the product, and booking.</p>
<h2>What a typical first version contains</h2>
<p>A typical first version had 5 building blocks. The range was 1 to 10. The blocks we built most often:</p>
<table>
<thead>
<tr>
<th>Building block</th>
<th>Builds (of 43)</th>
</tr>
</thead>
<tbody><tr>
<td>Operator dashboard</td>
<td>23</td>
</tr>
<tr>
<td>Payments</td>
<td>21</td>
</tr>
<tr>
<td>Notifications</td>
<td>18</td>
</tr>
<tr>
<td>Booking or scheduling</td>
<td>17</td>
</tr>
<tr>
<td>Search</td>
<td>16</td>
</tr>
</tbody></table>
<p>Only 4 of the 43 named an AI feature, and only 3 named direct messaging between users. The things people assume every MVP needs are not what most of these products shipped first.</p>
<h2>Which blocks added time</h2>
<p>Counting blocks did not predict build time. Across the 41 apps with a recorded build time, the correlation was about zero. What mattered was which blocks you picked.</p>
<ul>
<li>Connecting to an outside system (an airline fare system, email sync, a supplier network) averaged 7.7 weeks to a first version, against 6.8 weeks without one. It was the clearest time-adder in the data.</li>
<li>Taking payments added nothing. Builds with payments averaged 7.1 weeks and builds without averaged 7.2.</li>
</ul>
<p>The takeaway for scoping: payment platforms are a solved problem. Other people's systems are not. If your first version depends on someone else's API, data or approval process, budget for that first.</p>
<h2>Marketplaces are a different shape</h2>
<p>16 of the 43 were marketplaces. 12 of those took payments, 8 verified the people on the supply side, and 5 held money in escrow until the job was done. Outside marketplaces, verification showed up in only 2 of 27 builds.</p>
<h2>Caveats</h2>
<p>This is our own work, not a market survey. It only covers builds that launched, and each feature list is the headline features as written in our case studies, coded by hand into blocks. Treat it as a reference point, not a benchmark.</p>
<p>The full method, the coded dataset and a PDF version are on our research page: <a href="https://aibrevo.com/research/mvp-features-43-builds/">https://aibrevo.com/research/mvp-features-43-builds/</a></p>
]]></content:encoded></item></channel></rss>