Application templates
Start where a SaaS product is after its first year.
A working multi-tenant application, with single sign-on, two-factor authentication, roles and teams, billing and an audit log already built and tested. Its documentation and feature specifications come into your workspace with it, so your first coding session builds your product, not its plumbing.
Identity & Access
Single sign-on
Let your team sign in through your own identity provider - Google Workspace, Microsoft Entra ID, or any SAML 2.0 IdP.
Identity provider
Email domains
northwind.exampleSign-in policies
Require SSO
Members can no longer sign in with a password or Google. Owners stay exempt, so the organization cannot lock itself out.
What's built
Down to the details that usually come later.
Five parts every business application needs, built and tested, and wired to each other.
Read moreWhat the template includes
Organizations
Identity & Access
Multi-factor authentication
Require everyone to confirm a code from an authenticator app after their password, and see who has already set one up.
Enforcement
Require multi-factor authentication
Every member has to confirm a code from an authenticator app after their password. Members without one are walked through setup on their next sign-in and cannot use the app until they finish.
1 member is signed out until they enrol. Required since 28 Oct 2026.
Identity & Access
- Mia Lundmia@northwind.exampleOwner
- Theo Vancetheo@northwind.exampleAdmin
- Ines Duarteines@northwind.exampleMember
- Omar Haddadomar@northwind.exampleViewer
Billing
Plan
teamPer seat
EUR 72.00
a month
4 seats x EUR 18.00 · Renews on 1 Dec
21 Oct · Seat added for Omar Haddad, proratedEUR 6.60
Invoices
- 1 Nov 2026INV-0031EUR 78.60Paid
- 1 Oct 2026INV-0027EUR 54.00Paid
- 1 Sep 2026INV-0022EUR 54.00Paid
Identity & Access
- Mia Lund turned on Require SSOSingle sign-on2 min ago
- Mia Lund changed Theo Vance's role from Member to AdminUsers1 hour ago
- Theo Vance invited Omar Haddad as a ViewerUsers21 Oct
- Mia Lund changed the plan from starter to teamBilling12 Aug
Meet Software Inc, a fictional company that sells invoicing software. Every name in these pictures is sample data.
Built for agents
Your agents know it from the first session.
The template is written to be worked on by coding agents, and it comes into your workspace with what a coding session reads first.
Its specifications, with their rules.
Its feature specifications come into your workspace with their business rules, so a session on your copy starts from what the application already does.
Its documentation.
The application's documentation is in your workspace beside them, where coding sessions and the AI Assistant can use it.
Instructions for the agent.
Its repository tells an AI coding assistant how the application is built, for the whole of it and for each of its parts.
A style guide and a browser.
A style guide that shows the application's real components, and an end-to-end suite the agent can use to drive the running application.
Billing
Sample data
From the template to your product
Create it, change it, deploy it.
1Create
Pick the template, then create your application.
In Applications, choose Add application, then From a template, and Create application. Productmind copies its code into a private repository it hosts for you.
Applications
Add an application
Connect your application or start from an enterprise-ready SaaS template.
A working multi-tenant web application.
- Organizations and workspaces
- Users, roles and teams
- Single sign-on
- Two-factor authentication
- Billing
- Audit log
Already built and tested
Your copy includes
2Change
It opens ready to work on.
Its documentation and feature specifications are already in your workspace. Describe a change, and a coding session drafts a plan for you to approve, builds it and opens a pull request for you to review.
billing-portal
3Deploy
Every merge deploys to AWS.
On the Enterprise plan, in early access, each environment deploys to an AWS account Productmind manages for your workspace, or one your company connects. Every pull request merged into its branch deploys, under a domain your company owns. Your payment provider's keys go in as API secrets.
billing-portal
Source code
Cloud accounts
- Account
- AWS account 210987654321
- Branch
- Deploys from
main - Address
- portal.softwareinc.example
- Running now
- 4f9c2e1Annual plansDeployed1 hour ago
- Live at
- https://app.portal.softwareinc.example
Sample data
Read moreCloud accountsDomainsDeploys
Yours
Your code, in your own copy.
A private repository.
Productmind hosts your copy as a private repository, so coding sessions, previews and pull requests work on it straight away.
Work on it anywhere.
When it's on for your organization, choose Add me as a collaborator to get admin access to the repository, then clone it and push to it directly.
Take it with you.
The code is yours. Before you delete the application, ask Productmind to transfer the repository to your own GitHub organization, or for a copy of it.
The rest is yours to build.
The template is the part every business application needs. What makes it your product is what you build on it.
Read moreWorking on it outside ProductmindMoving it to your own GitHub organization