GrowthDesk: Protected CRM Developer Foundation

GrowthDesk is an independently designed and built Noerong developer foundation. I handled the product design, interface engineering, data model, owner access controls, testing and release package. Version 1.1 implements the owner lead-management core and shows clearly labelled previews of a larger CRM.

Service businesses spread enquiry and client information across forms, inboxes and spreadsheets. I explored that broader journey while making the implemented starting point explicit: capture an enquiry, protect staff access and update the lead stage.

A customer website and structured public enquiry capture.

Protected staff pages and APIs with signed owner sessions.

Stored lead records, stage updates and business settings.

Bounded input validation, same-origin writes and basic rate limits.

Visible errors and read-only controls in the fictional public showcase.

The inbox does not deliver messages. Automation settings do not execute provider workflows. Project creation, portal approvals, file downloads, payments and customer feedback collection need implementation. Illustrative charts are not earned revenue.

Three focused test groups and 27 HTTP checks passed, covering signed-out access, forged sessions, validation, same-origin writes and the enquiry-to-stage workflow. Lint and build passed. The extracted buyer ZIP also installed and built successfully with its sanitized configuration.

The stack uses React, TypeScript, Next-compatible routing through vinext, D1-compatible SQL storage, Docker and Railway. A customer installation needs a fresh persistent database, explicit production mode, random owner key and exact public origin. Individual staff accounts and multi-tenant roles need further development.

Open the read-only GrowthDesk demo · Read the current scope on Noerong

Get the developer foundation · Commission a scoped foundation setup

This is an independently designed and built Noerong product, not a commissioned client engagement. Sample records illustrate the workflow; no client revenue or conversion result is claimed.

Before using the source kit with real customer data, configure and verify the included single-owner access, random owner key and exact public origin. Individual staff accounts and team roles require additional development. Configure persistent storage, secrets, provider credentials, backups, and buyer-specific integrations. The source kit is a single-business foundation, not a turnkey multi-tenant SaaS.