The SuiteResources AI Application Platform Overview

Introducing the SuiteResources AI Application Platform

Every page on this site is built the same way. The blog post you're reading, the migration sign-up page, the deadline trackers — all of it runs through the same internal system. We've called it "PM" around here for months, short for Product Manager, and that name never really told anyone what it actually does. Going forward we're calling it what it is: the SuiteResources AI Application Platform.

Here's the rundown.

Two Jobs, One System

The platform does two things that sound unrelated until you've used it for a while.

First, it's a roadmap tool. Every idea we're considering, every feature we've committed to, every half-formed thought that might turn into either — it all lives in one place instead of scattered across Slack messages and a document nobody opens. An idea gets scored using the standard RICE framework (reach, impact, confidence, effort), broken into features, and tracked through to done. An AI coding agent, Claude Code, handles a lot of the grunt work: refining a TAM estimate, drafting a feature spec from a two-sentence idea, keeping the language on a six-month-old feature honest when the plan underneath it changes.

Second — and this is the part that actually saves time — it's the shared foundation every app we build sits on top of. The platform includes an SDK, so between the two, creating an application becomes the easy part. Knowing what to create becomes the most important piece of the puzzle.

What the SDK Actually Gives You

Before the SDK existed, every new app reinvented the same handful of things, usually slightly wrong each time. Now they don't.

Single sign-on. Log into one SuiteResources app and you're logged into all of them. Nobody builds their own auth flow anymore.

AI conversation persistence. Close the tab mid-conversation with an AI assistant inside any app, come back later, and it's still there.

Feedback and CSAT, built in. Every app gets the same feedback button and the same prompted satisfaction survey, instead of each one bolting on its own version.

An MCP server for every app. This is the one that makes agents like Claude actually useful here. Instead of clicking through a UI, an AI agent can be handed direct, permissioned access to an app's data. It's how this blog post is getting published, actually.

A shared outbound connector to NetSuite, so any app that needs to reach into a customer's NetSuite account isn't hand-rolling its own MCP client.

Threaded notes, @mentions, and notifications — the collaboration layer every internal tool needs eventually, built once.

Analytics and telemetry. Usage data across every app in the platform: which users are using which apps, what AI token costs look like per app, and so on.

Scheduled jobs and heartbeats. Every app can create cron jobs to process queues, while heartbeat monitoring tells us whether the various apps are alive and keeping up.

Payment processing via Stripe. Any app that needs to sell something can — ACH, credit cards, covered.

Abandoned cart and payment-request follow-up. As a concrete example: any prospective client who has signed up for a SuiteScript migration and been approved, but hasn't completed the transaction, gets a polite nudge by email. After a prescribed number of days the payment request ages off the list. If payment does come through later, everything picks up cleanly and the client gets scheduled for their migration.

None of this is exciting in isolation. Auth, notifications, an AI conversation that doesn't vanish when you refresh the page — nobody writes a blog post about wanting those things. But multiply "reimplemented slightly wrong" by however many apps we end up building, and it compounds quickly. The entire point is building these things once and bolting new apps onto them rather than rebuilding from scratch every time.

What's Coming

Two items are near the top of the backlog: single-use Stripe coupon codes and user invitations, so an existing user can bring someone else into an app directly.

For now: the next time you fill out a contact form on this site, or a migration payment goes through, you're running on the SuiteResources AI Application Platform. You just didn't know it had a name.