The engineering problemPresent CAD automation consulting authority, offers, industries, and proof.
Two consulting brands, a large public authority graph, paid discovery, opportunity operations, document generation, and controlled external connectors needed one typed platform without blending brands or allowing accidental external mutations.
Component responsibilityWhat this part of the system owns
Owns CAD Guardian's engineering-automation positioning, solution graph, case stories, offers, procurement, and conversion routes.
The repository demonstrates full operating-system thinking: hostname-aware public experiences, deterministic commercial routing, connector safety, CRM and payment boundaries, generated authority artifacts, and a manually controlled release pipeline.
- Primary platform
- Next.js / Node / CLI
- Interface
- Next.js
- System relationship
- Opportunity Platform
- Priority
- Flagship
Operating flowHow inputs become controlled outputs
Inputs- Buyer, recruiter, and public-search requests
- Typed offers, project records, opportunity signals, and approved evidence
- Explicit operator commands for external connectors and releases
System behavior- Resolve brand and route intent
- Apply deterministic qualification, safety, attribution, and publication rules
- Generate public experiences, internal decisions, documents, or controlled connector actions
Outputs- Brand-specific consulting and software journeys
- Qualified opportunities, quotes, payment acceptance, and operational plans
- Certified public artifacts, reports, sitemaps, and releases
Why the solution is shaped this way
Run both brands from one typed Next.js platform with hostname-aware routing.
Why: Shared engineering, evidence, and release infrastructure can evolve once while each brand retains canonical ownership and buyer intent.
Tradeoff: Every public registry and route must enforce brand separation and wrong-host behavior.
Make external connector workflows dry-run-first with explicit execution flags.
Why: Opportunity and evidence automation can be inspected before it changes Gmail, Drive, CRM, contacts, calendars, or GitHub.
Tradeoff: Operators perform a deliberate second step for approved mutations.
Keep local certification authoritative and hosted automation manual-only.
Why: One certified artifact can be inspected and promoted without repeated GitHub or Vercel builds.
Tradeoff: Release ownership remains an explicit operator responsibility.
How the solution is structured and verified
Solution shape
- Dual-brand Next.js App Router application
- Typed enterprise content and portfolio registries
- Server-side revenue and connector harness
- Local document, audit, evidence, and release tooling
Framework and package signals
- Next.js 16
- React 19
- TypeScript
- Node.js 24
- better-sqlite3
- Neon serverless Postgres
- Stripe
- Google APIs
- HubSpot integration
- Vitest
- Playwright
- Biome
Executable surfaces
- Two public hostname experiences
- Internal revenue and quote workspaces
- Connector and revenue CLI commands
- Local certification and prebuilt deployment commands
Verification
- Brand-host and authority-graph unit tests
- Revenue safety and Stripe webhook tests
- SEO/AEO, sitemap, search, and public-route audits
- Multi-viewport Playwright verification and production build
What Thomas built
Thomas designed and implemented the shared platform, its brand architecture, public content systems, revenue harness, connector controls, payment flow, document generation, audits, and release process.
Technical compositionTechnologies, logic, and connected outputs
TypeScriptNext.js 16React 19Neon PostgresSQLiteHubSpotStripeGmail/Google APIsNext.js / Node / CLI
Algorithms and domain rules
- Classification
- deduplication
- scoring
- routing
- dry-run execution
- evidence validation
Integrations and data
- Neon
- SQLite
- HubSpot
- Stripe
- Gmail
- Google Drive
- GitHub
- Google Contacts
- Google Calendar
- Search Console
- IndexNow
- Neon Postgres
- generated Markdown/JSON reports
Outputs and runtime
- Next.js
- Website
- Vercel / local operator tooling
Libraries and architecture
- One typed Next.js platform with runtime brand separation, connector adapters, local/remote persistence, and explicit release gates
- Next.js 16
- React 19
- Neon Postgres
- SQLite
- HubSpot
- Stripe
- Gmail/Google APIs
- Neon serverless
- better-sqlite3
- Biome
- Vitest
- Playwright
- Tailwind CSS
What an evaluator can inspect
Confidence: High. This portfolio distinguishes delivered applications, supporting components, tests, libraries, utilities, and repository containers.
The implementation summary was derived from reviewed solution files, project or package manifests, architecture documentation, and test surfaces. Private locators, source code, secrets, and proprietary rules are not published.
- Application manifest and executable command surface (manifest)
- Hostname routing and deployment configuration (architecture)
- Revenue scoring, persistence, and connector safety modules (architecture)
- Authority, revenue, payment, and browser verification suites (tests)
- Private source locations, customer data, proprietary rules, and raw implementation material are withheld.
Portfolio source review
The public record summarizes application purpose and composition. Private paths, source, customer data, proprietary rules, and restricted artifacts are not published.
