A: Thanks for the thoughtful insight—especially from someone with deep experience in approval flows across enterprise systems.

Before addressing your questions directly, I want to clarify our target market. ApproveThis isn't meant to compete with full-scale enterprise ERP systems. One of the reasons I founded the company was my experience managing a six-month, $100K ERP implementation. We aim to bridge the gap between chaotic Slack/email approvals and the cost/complexity of larger systems. If you're in that middle ground, ApproveThis is probably for you.

Some of your points are a bit open-ended, so I’m happy to continue the conversation by email or over a call.

Q1: Is ApproveThis configurable enough to reflect the unique approval processes of different organizations?

Yes. With workflow-level routing, approval thresholds, groups, and optional form customization, ApproveThis is designed to adapt to many different approval structures. You're right that our docs haven't kept pace with recent feature releases—we're fixing that now.

Q2: Can the system support different approval flows for different types of requests (e.g., CapEx, board approvals, acquisitions)?

Yes. You can configure a unique workflow for each request type, each with its own logic, form, and initiator.

Q3: Does configuration happen at the individual process level rather than only at the account level?

Yes. There is no limit on the number of processes. Each workflow can start from its own form, integration, or mailbox.

Q4: How adaptable is the platform to real-world, enterprise-level use cases where approval processes vary widely?

We intentionally favor simplicity and fast adoption over deep complexity. That said, the platform does support routing, thresholds, multi-step approvals, and escalation logic.

Q5: Are there demo videos available to illustrate how flexible ApproveThis is for complex approval workflows?

We’re currently recording new videos to reflect our UI overhaul. You can book a live demo at https://cal.com/approve-this or reach me at [email protected].

Q6: What are the approver limits per plan, and are they sufficient for real-world approval chains (e.g., ops managers, directors, finance)?

The plans on AppSumo and our public site have limits designed for SMBs. We keep those limits in place to encourage larger orgs with complex needs to connect with our sales team. Larger implementations usually need deeper onboarding and ongoing support, which aren’t feasible at lifetime deal pricing.

Q7: Does the system support conditional approval logic based on variables like cost or strategic alignment?

Yes. You can route based on numeric thresholds, category fields, or even custom text fields in the request.

Q8: Is the platform suitable for small businesses that still need multi-step approval processes?

Yes—that’s our primary audience. But we also support teams inside larger orgs who need simplicity and speed.

Q9: Why is the integration suite excluded from Tier 1, and is that decision limiting adoption?

Great question. In short: users who leverage integrations tend to receive more value, and also require more support. For sustainability, we charge more for that tier—even if it slows initial adoption.

Q10: Is integration actually necessary for adoption, or should development focus instead on core approval functionality?

We agree that core approval features are essential. We consider those stable now, and we’re currently focused on improving UX and building additional integrations. Most of the capabilities you mentioned already exist—we just need to better showcase them.

Q11: Does ApproveThis generate a unique reference ID for each approval record to ensure traceability?

Yes. Every request and every individual approval within a request has its own unique ID.

Q12: Is the user interface intuitive enough for non-admin users to easily understand and use the platform?

Yes. Most users never log in—they approve by email. And if they do log in, they get a clean, focused dashboard showing exactly what they need to review.

Q13: Does ApproveThis support admin and user role separation to manage access and permissions?

Yes. We support multiple roles including Admin, Manager, User, Read-Only, and Unregistered (for users who can only view requests they've been assigned to).

Q14: Are there plans to raise the user limits for teams that need broader access?

Companies with larger user bases or more complex needs should meet with our team to ensure a good fit and proper onboarding. We don’t plan to expand user limits in base plans at this time.

Q15: What is the long-term vision and sustainability of ApproveThis?

We’re self-funded, profitable, and continue to grow month over month. We focus on product-led growth, but recently have spent more time shipping features than updating our sales pages and documentation (which is why you've found some of it out of date). We'll have everything back up to date shortly.

Continued Below 👇