Public
Remixed
AFLABS PM — projects, partners, and client timelines
Val Town is a collaborative website to build and scale JavaScript apps.
Deploy APIs, crons, & store data – all from the browser, and deployed in milliseconds.

AFLABS PM

A full Val Town operations workspace for AFLABS administrators, internal users, and partners.

Runtime

  • Val Town React + Hono
  • Selectable Neon Postgres or Turso/libSQL database
  • Phone-and-PIN authentication for internal users and partners
  • Secret project URL plus PIN for clients
  • Cookie-backed sessions
  • Val Town std/openai for AI project extraction, proposals, and business pitch generation

Required environment variables

  • DATABASE_PROVIDER (neon or turso)
  • NEON_DATABASE_URL when using Neon
  • TURSO_DATABASE_URL and TURSO_AUTH_TOKEN when using Turso
  • CACHE_ENABLED (true or false)
  • APP_BOOTSTRAP_TOKEN
  • SESSION_SECRET

The selected database provider is permanently recorded in Val-scoped blob storage on first use. Changing DATABASE_PROVIDER later fails safely.

Main capabilities

  • Lead pipeline with stage overview, reminders, requirements, complete audit timeline, and one-to-many project conversion
  • Mandatory lead origin for new projects and attachment flow for legacy projects
  • Project filters for type, due date, stage, and partner
  • Scoped one-to-one AFLABS ↔ partner conversation threads for a single lead or project
  • Project one-line summaries plus Markdown working notes
  • Basic, advanced, and custom partner permission packages
  • Itemized invoice PDFs with quantity, unit price, discount, arrears, optional tax, and totals
  • Commercial cost preview for regular cost, partner-managed cost, spread, tax, and client total
  • AI Business Idea Pitch Generator for admins and eligible partners
  • Admin-configurable AI pitch and proposal prompts stored in application settings
  • Partner MoU templates, published agreement versions, monthly targets, achievement metrics, and target history
  • Admin and partner dashboards with pipeline, delivery risks, revenue, meetings, unread threads, and target trajectory
  • Meeting availability and blocking, quota enforcement, collision prevention, lead/project context, and online/offline venue
  • Existing delivery Kanban, milestones, stakeholders, payments, branded proposals, recurring projects, client portal, and activity history

Data evolution

The growth-suite schema is created idempotently on authenticated API requests. Existing project records remain valid and can be attached to a lead later; all newly created projects require an originating lead.