Enterprise & upmarket waitlist

We don't pretend to be enterprise-ready yet.

GuideSpend works best at 50–150 employees today. If you're 150–500, there are real gaps between what we ship and what your IT and finance teams will ask for. This page lists every one of them honestly, what the current workaround is, and when we plan to close it.

What we don't ship yet

  1. SAML / SSO

    Today
    Google and Microsoft OAuth sign-in only. No SAML, no SCIM provisioning, no Okta / Entra / JumpCloud integration.
    Roadmap
    Target Q3 2026 alongside the SOC 2 Type I audit window. SCIM will follow once a first design partner is running on it.
    Why it matters
    Okta-standardized IT orgs reject vendors without SAML in security review. This is the #1 blocker reported by 200+ seat prospects.
  2. ERP ingestion

    Today
    CSV upload only. No direct connectors to QuickBooks Online, NetSuite, Xero, or SAP.
    Roadmap
    QuickBooks Online is the first target — it's the most common small-to-mid market ERP and the fastest to ship. NetSuite and Xero follow based on waitlist demand.
    Why it matters
    Without ERP sync, finance ops copy-paste vendor lists and invoice totals. That's the exact work GuideSpend is sold to eliminate.
  3. Multi-currency

    Today
    Spend is captured in a single base currency per org. No conversion, no per-contract currency tagging.
    Roadmap
    Planned. Holding the work until a design-partner with a real multi-currency footprint is on the waitlist — we'd rather ship the right model than a premature one.
    Why it matters
    Blocking for any org with EU, UK, or APAC subsidiaries. Roll-ups and renewal exposure become misleading without currency tagging.
  4. Approval workflows

    Today
    Binary RBAC (org_admin, org_member). Effective roles (CFO / Admin / Finance Ops) exist but there are no threshold-based approval chains or policy enforcement.
    Roadmap
    v1 target: single-approver, threshold-based (e.g., any renewal above $25k requires an approver). Multi-stage approvals follow.
    Why it matters
    Above roughly $50k of annual vendor spend, finance leaders need signoff trails that pass an audit. Without them, governance claims are aspirational.
  5. Public API and webhooks

    Today
    Internal /api/v1/* exists as compatibility aliases for our own clients. No published developer documentation, no issued API keys, no webhook surface.
    Roadmap
    Planned after SSO. We want to harden tenancy and rate-limiting on the existing surface before we document it externally.
    Why it matters
    Integration partners (procurement tools, Finance data lakes, Slack ChatOps) need a stable public API. Its absence is a common disqualifier.

Current fit by company size

  • 50–150 employeesGood fit today

    This is our wedge. The hero workflow (trial → import → normalize → renewal exposure → exec pack → reminders) is the tightest path and our pricing matches.

  • 150–300 employeesPartial fit — join waitlist

    Partial fit. Business tier covers most needs, but expect to run alongside spreadsheets for SSO-gated and ERP-heavy workflows until the gaps above close.

  • 300–500 employeesTalk to us first

    Not a fit yet for most orgs. If you have a specific gap you can stay on CSV imports to solve, email us — otherwise the waitlist is the honest answer.

Tell us which gap matters most

We prioritize roadmap items by waitlist demand — the more prospects who name a specific gap, the sooner it ships. There's no form on this page deliberately. A short email gets you a real answer from a real person, not a drip sequence.

Email sales@guidespend.com

We keep your details confidential and only use them to prioritize roadmap work and reach back out when a relevant capability ships.

In the meantime

  • Our pricing page shows what Starter, Pro, and Business cover today. Starter and Pro sign up self-serve with no card.
  • Our security page is the full IT-review packet: MVSP self-assessment, subprocessor list, and the Q3 2026 SOC 2 Type I target.
  • Our status page shows live app health and links to every infrastructure provider we depend on.
  • Our changelog lists recent shipped work so you can see the cadence.