Why we publish our roadmap publicly (and what's coming July 1)

    <!-- Timeline -->
    <g transform="translate(60,200)">
        <line x1="0" y1="0" x2="1080" y2="0" stroke="rgba(255,255,255,0.2)" stroke-width="2"/>

        <g transform="translate(60,0)">
            <circle r="14" fill="#93AB49"/>
            <text y="-30" fill="#93AB49" font-family="system-ui,sans-serif" font-size="11" font-weight="700" letter-spacing="1.5" text-anchor="middle">SHIPPED</text>
            <text y="40" fill="#ffffff" font-family="system-ui,sans-serif" font-size="13" font-weight="600" text-anchor="middle">Past Perf</text>
            <text y="58" fill="rgba(255,255,255,0.6)" font-family="system-ui,sans-serif" font-size="11" text-anchor="middle">v0.7 · Apr</text>
        </g>
        <g transform="translate(280,0)">
            <circle r="14" fill="#93AB49"/>
            <text y="40" fill="#ffffff" font-family="system-ui,sans-serif" font-size="13" font-weight="600" text-anchor="middle">RACI Matrix</text>
            <text y="58" fill="rgba(255,255,255,0.6)" font-family="system-ui,sans-serif" font-size="11" text-anchor="middle">v0.8 · Apr</text>
        </g>
        <g transform="translate(500,0)">
            <circle r="14" fill="#B31942"/>
            <text y="-30" fill="#B31942" font-family="system-ui,sans-serif" font-size="11" font-weight="700" letter-spacing="1.5" text-anchor="middle">IN-FLIGHT</text>
            <text y="40" fill="#ffffff" font-family="system-ui,sans-serif" font-size="13" font-weight="600" text-anchor="middle">PDF Templates</text>
            <text y="58" fill="rgba(255,255,255,0.6)" font-family="system-ui,sans-serif" font-size="11" text-anchor="middle">v0.9 · May</text>
        </g>
        <g transform="translate(740,0)">
            <circle r="18" fill="#ffffff" stroke="#B31942" stroke-width="3"/>
            <text y="-30" fill="#ffffff" font-family="system-ui,sans-serif" font-size="11" font-weight="700" letter-spacing="1.5" text-anchor="middle">LAUNCH</text>
            <text y="40" fill="#ffffff" font-family="system-ui,sans-serif" font-size="13" font-weight="600" text-anchor="middle">v1.0</text>
            <text y="58" fill="#B31942" font-family="system-ui,sans-serif" font-size="11" font-weight="700" text-anchor="middle">JULY 1</text>
        </g>
        <g transform="translate(960,0)">
            <circle r="14" fill="rgba(255,255,255,0.2)" stroke="rgba(255,255,255,0.3)"/>
            <text y="-30" fill="rgba(255,255,255,0.5)" font-family="system-ui,sans-serif" font-size="11" font-weight="700" letter-spacing="1.5" text-anchor="middle">NEXT</text>
            <text y="40" fill="rgba(255,255,255,0.85)" font-family="system-ui,sans-serif" font-size="13" font-weight="600" text-anchor="middle">Cost Volume</text>
            <text y="58" fill="rgba(255,255,255,0.6)" font-family="system-ui,sans-serif" font-size="11" text-anchor="middle">Q3 2026</text>
        </g>
    </g>
</svg>

Most B2B SaaS hides the roadmap. We don't. The full VETR roadmap is at vetrproposal.com/roadmap — every shipped feature, every WIP epic, every backlog item with rough dates. Customers vote on what comes next. Here's why we built the platform this way and what's landing on July 1.

Why public

Three reasons. None of them are marketing.

1. SDVOSBs are skeptical of vendors, and they should be

The federal contracting space is full of tools that promise the moon and ship a ticketing system. Founders are right to ask "what have you actually built and what are you actually building next?" before signing a 24-month commitment. A locked roadmap is a trust signal, not a competitive risk.

2. We win when customers help us prioritize

The platform serves your bidding workflow. We do not know more about your day than you do. The roadmap voting widget on each item lets you upvote what would unblock you next week. We read those votes — every Friday, in fact, the team scrubs the new votes and rebalances the next sprint.

3. Acu-Elligent's transparency value

VETR is part of Acu-Elligent, the parent brand. Acu-Elligent's commitment is "every interaction transparent." That isn't a marketing bullet — it shapes how we run engineering. The roadmap is the surface of that commitment. So is the public changelog. So is the quarterly compliance report.

What's shipping July 1

Here's the launch slate. Every item below is either in-flight or already shipped behind the founding-member flag. Public release date is the same: July 1, 2026.

• VETR Score™ on every RFP — the four-pillar Win Probability with AI commentary, available on every uploaded RFP. Shipped behind flag.
• Auto-built compliance matrix — Section L "shall" extraction + Section M criteria mapping, with status tracking through the proposal lifecycle. Shipped behind flag.
• Past-performance library with STAR narratives — structured Situation/Task/Action/Result for every contract; auto-pull into proposals. Shipped.
• Teaming RACI matrix — define R/A/C/I per partner per requirement, export to teaming agreements. Shipped.
• Four PDF templates — Classic, Modern, Government, Executive cover styles for proposal export. Shipped behind flag.
• SAM.gov integration — pull active opportunities by NAICS + set-aside; link to your saved searches. Shipped.
• FPDS integration — historical award data on agencies + competitors. Shipped.
• 14-day trial, no credit card — try every feature, score three RFPs, see real value before committing. Live July 1.
• Founding-member pricing — 24-month price lock — first 100 SDVOSBs lock $149 Startup or $299 Professional for 24 months. Live July 1.

What's NOT in v1.0 (and why)

We made hard choices about what doesn't ship on day 1. Some of these are on the public roadmap with target dates; some need more discovery work first.

• Mentor Marketplace — connecting SDVOSBs with mentor-protégé large-business primes. Target: Q4 2026. We need legal review of the matchmaking liability before we open this.
• Cost Volume builder — full price-volume support with WBS templates and indirect-rate import. Target: Q3 2026. Currently the platform supports a basic cost summary; the full builder is in design.
• Native mobile apps — iOS/Android. Not on roadmap. The proposal workflow is not mobile-first; we'd rather invest those engineering hours in the desktop experience.
• White-label / agency mode — let proposal consulting firms run VETR for their clients. Target: 2027. Several capture-consulting firms have asked; we need to figure out the data-isolation model first.

How to vote

Every item on /roadmap has an upvote button. You don't need an account to view; you need one to vote. The Friday rebalance reads the new votes and reweights the upcoming sprint backlog accordingly. Your vote matters more in the first 90 days post-launch than it ever will again.

Try VETR before launch

The closed beta is open through June 22. If you're an SDVOSB actively bidding on federal contracts, request beta access — five seats remain, and beta participants get lifetime founding-member status.