Build PulseBoard for SaaS teams. Customers sign in, share feedback, vote, and upgrade their workspace to Pro. Take it from Test to a complete company launch.
- PERCO Waiting for project context
- Founder intent Idea captured
Guided demo · Illustrative workflow
See one idea become a live company.
Follow PulseBoard from a founder's request to a live product, customer-owned domain, company email, and verified launch receipt.
This guided demo uses example data and does not perform real purchases, provision accounts, or modify production infrastructure.
Guided demo · Illustrative workflow
PulseBoard guided idea-to-company demo
Guided demo · Illustrative workflow
npx -y @percoai/cli@0.1.3 login --env stage
npx -y @percoai/cli@0.1.3 link --canvas-id "$CANVAS_ID" --agent codex --env stage
npx -y @percoai/cli@0.1.3 mcp install --client codex --scope user --project "$CANVAS_ID" --env stage
- Canvas
- canvas_pulseboard_demo
- Project
- PulseBoard
- Coding agent
- Codex
- Environment
- Stage
- MCP connection
- Ready
- CLI Starting browser login
- Browser Approval requested
- Account Signed in
- Canvas Connected
- MCP connection Ready
You + coding agent
- Account flow
- Feedback model
- Voting UI
- Pro-plan UI
- Playwright journey tests
PERCO platform
- PostgreSQL
- Redis
- Project Vault
- Test
- Production
- Domain and TLS
- Company email
- Coding agent Account flow building
- PERCO PostgreSQL selected
- Coding agent Feedback model built
- PERCO Redis selected
- Coding agent Voting UI built
- PERCO Test isolated
- Coding agent Pro-plan UI built
- Coding agent Journey tests created
- PERCO Production gated
| Product need | Application responsibility | PERCO component | Why |
|---|---|---|---|
| Sign-in | Coding agent implements account behavior. | Application configuration and scoped secrets. | Keeps business logic in the app and credentials outside the repository. |
| Feedback and votes | Coding agent creates the model and user experience. | PostgreSQL. | Durable transactional records. |
| Trending requests | Coding agent uses cached counters. | Redis. | Fast reads and lower database load. |
| Pro checkout | Coding agent implements the product flow. | Payment configuration, secrets, and deployment wiring. | Keeps provider credentials scoped and auditable. |
| Acceptance testing | Coding agent creates user-journey tests. | Isolated Test environment and evidence store. | Prevents unverified changes from reaching Production. |
| Source management | Coding agent commits application code. | Managed GitLab project and pipeline. | Gives the customer an owned, reviewable code history. |
| Public website | Application build supplies the product. | Production, domain, DNS, TLS, and health gate. | Publishes only the approved, healthy release. |
| Company email | Founder chooses mailbox names. | Mailbox provisioning and email DNS. | Gives the company a verified identity for customer communication. |
- Target environment
- Test
- Plan state
- No changes applied yet
- Cost category
- Application runtime — Included in approved Test estimate
- Cost category
- Managed data — Included in approved Test estimate
- Cost category
- Domain and company email — Included in approved launch estimate
- Risk
- Production remains gated
- Risk
- No data migration
- Risk
- Domain registration and mailbox setup wait for Launch approval
- Primary action
- Approve for Test
- Target environment Test
- Plan state No changes applied yet
- Functions 8 needs mapped
- Estimate Cost categories visible
- Risk Reviewed
- Human approval Approved for Test
- A user can create an account and sign in. Coding agent Passed
- A signed-in user can submit feedback. Coding agent Passed
- A second user can vote on that feedback. Coding agent Passed
- A workspace can open the Pro checkout flow. Coding agent Passed
- Application health and required service connections are ready. PERCO Passed
- GitLab project created
- Default branch protected
- Pipeline passed
- Customer owns the repository
- Environment Test
- Account journey Passed
- Feedback journey Passed
- Voting journey Passed
- Pro checkout journey Passed
- Application health Passed
- GitLab project Created
- Default branch Protected
- Pipeline Passed
- Repository ownership Customer
pulseboard.app
- Registrant
- PulseBoard
- Ownership
- Customer
- Renewal
- Managed
- DNS
- Configured
- TLS
- Active
- Charge
- Included in approved launch estimate
- Launch plan Approved
- pulseboard.app Purchased for PulseBoard
- DNS Configured
- TLS Active
- Ownership Customer
- hello@pulseboard.app
- support@pulseboard.app
- MX configured
- SPF passed
- DKIM verified
- DMARC active
- Test email delivered
- hello@pulseboard.app Ready
- support@pulseboard.app Ready
- MX Configured
- SPF Passed
- DKIM Verified
- DMARC Active
- Test email Delivered
- Product websiteOnline
- Source repositoryReady
- Test journeysPassed
- Production healthHealthy
- Company domainActive
- TLSActive
- Company mailboxesReady
- Mail deliveryVerified
Idea in the terminal. Product, domain, email, and production online.
- Product website Online
- Source repository Ready
- Test journeys Passed
- Production health Healthy
- Company domain Active
- TLS Active
- Company mailboxes Ready
- Mail delivery Verified
- Launch Idea in the terminal. Product, domain, email, and production online.
Guided demo · Illustrative workflow
pulseboard.app
- Product websiteOnline
- Source repositoryReady
- Test journeysPassed
- Production healthHealthy
- Company domainActive
- TLSActive
- Company mailboxesReady
- Mail deliveryVerified
Idea in the terminal. Product, domain, email, and production online.
Transcript
Guided demo · Illustrative workflow
This guided demo uses example data and does not perform real purchases, provision accounts, or modify production infrastructure.
Start with the company you want to build.
A founder types the PulseBoard outcome in product language. PERCO waits for project context and does not ask the founder to design infrastructure.
Run PERCO from npm, sign in, and connect the project.
The pinned npm CLI opens an illustrative browser sign-in approval, links the Stage Canvas to Codex, and reports that the MCP connection is ready. No infrastructure approval happens in this login step.
The coding agent builds the product. PERCO prepares everything it needs to run.
The left pane credits the founder and coding agent with application behavior and product tests. The right pane credits PERCO with the database, cache, secrets, environments, domain, email, and dry-run platform plan.
See what will change, why it is needed, and approve the Test release.
Canvas maps eight product needs to application responsibilities and PERCO components, with reasons, cost categories, risk, and the Test target. It explicitly says that no changes are applied before approval.
Test the complete customer journey before production.
The Test environment runs the five declared customer and health journeys. The coding agent owns product-specific tests; PERCO provides Test and evidence. The illustrative GitLab project is customer-owned and its pipeline passes.
PERCO purchases the approved domain for the company and connects it to the product.
After launch approval, the illustrative workflow purchases pulseboard.app for PulseBoard, with the customer as owner, then configures DNS and activates TLS.
PERCO gives the company its inbox and verifies mail delivery.
The provider-neutral workflow prepares hello and support mailboxes, verifies MX, SPF, DKIM, and DMARC, and records an illustrative successful test delivery.
One idea becomes an online product and a company ready to operate.
PulseBoard appears at the illustrative domain while the launch receipt confirms the website, source, tests, Production health, customer domain, TLS, mailboxes, and mail delivery.
- A founder types a product outcome for PulseBoard while PERCO waits for project context.
- The request includes sign-in, feedback, voting, a Pro upgrade, Test, Production, a source repository, a domain, and company email.
- PERCO CLI version 0.1.3 starts an illustrative browser sign-in approval from npm.
- Sign-in completes; the Stage Canvas connects to Codex and the MCP connection reports Ready.
- The founder and coding agent build account, feedback, and voting behavior plus product tests.
- PERCO assembles PostgreSQL, Redis, scoped secrets, Test, gated Production, domain, TLS, and company email as a dry-run plan.
- Canvas maps eight product needs to application and PERCO responsibilities for the Test environment. No changes have been applied.
- Cost categories and risk are visible; the founder reviews the plan and approves it for Test only.
- In Test, account creation, sign-in, feedback submission, voting, and the Pro checkout journey pass.
- Application health passes; an illustrative customer-owned GitLab project has a protected branch and passing pipeline.
- The approved illustrative launch plan purchases pulseboard.app for PulseBoard, with ownership assigned to the customer.
- DNS is configured and TLS becomes active; PERCO manages the workflow but does not own the domain.
- Provider-neutral hello and support mailboxes become ready, and MX is configured.
- SPF passes, DKIM is verified, DMARC is active, and an illustrative test email is delivered.
- PulseBoard appears online while the receipt confirms website, source repository, Test journeys, Production health, and company domain.
- The receipt confirms TLS, company mailboxes, and mail delivery. The final result remains a guided illustrative workflow.
Your product, your boundaries