← Selected work

BUSINESS PLATFORM · PRODUCT ENGINEERING · AI AUTOMATION

05

Olmem Tech Platform

The customer-facing platform for a software business offering websites, custom workflows, CMS products, and AI systems.

PYBehavior → Cohorts
Signals → Recommendations

Small businesses often operate through disconnected spreadsheets, repetitive customer communication, hard-to-update websites, and generic tools that do not reflect their actual workflow. They may know where time is being lost but not how to translate that need into a maintainable software product.

I created Olmem Tech to offer the kind of problem-first engineering I use internally: understand the workflow, identify the constraint, and build the smallest useful system that removes friction. The website itself needed to explain complex technical services clearly, qualify needs, and support the path from discovery to purchase and ongoing service.

The responsive Next.js platform organizes website solutions, custom CMS products, workflow applications, and AI automation into clear service paths. It includes account experiences, product intake, authentication, database-backed workflows, payment integrations, SEO-focused pages, and reusable product architecture deployed through Vercel.

A simplified view of how information moves through the solution.

Technology choices were made around operating constraints, maintainability, integration boundaries, and the people using the system.

Framework

Next.js / React

One full-stack framework supports SEO-ready marketing pages, interactive intake experiences, server routes, authentication, and reusable product components.

Language

TypeScript

Types protect service configuration, form payloads, customer records, and payment-related state as the platform grows.

UI

Tailwind CSS

A shared utility system supports fast iteration and consistent responsive components across many service and product pages.

Database

PostgreSQL

Relational data fits customers, subscriptions, content, intake records, product state, and administrative workflows.

API

Stripe

Hosted payment flows reduce the amount of sensitive payment handling inside the application while supporting deposits and recurring services.

AI

Anthropic / OpenAI APIs

Provider integrations enable tailored chat, lead handling, and workflow assistance while guardrails keep each use case bounded and the application remains independent from one model vendor.

Cloud

Vercel

Native Next.js deployment, environment management, and continuous delivery keep product changes simple to release and observe.

Languages

TypeScript · JavaScript

Frameworks

Next.js · React · Tailwind

Databases

PostgreSQL

Cloud

Vercel

Machine Learning

AI-ready workflows

AI

Anthropic · OpenAI · Guardrailed chat

APIs

Stripe · Email · AI providers

Deployment

GitHub · Vercel CI/CD

HARDEST CHALLENGE

The hardest product challenge was making several related offers feel clear rather than overwhelming. Websites, CMS products, custom applications, maintenance, hosting, and AI automation solve different needs and require different intake paths.

HOW I SOLVED IT

I separated the information architecture by customer problem, created focused service pages and calls to action, and connected each offer to the appropriate intake, account, or payment flow.

LESSON LEARNED

Technical capability is not enough. A product must help a user recognize their problem, understand the solution boundary, and know exactly what to do next.

Concise implementation patterns that show the engineering beneath the interface.

typescriptProblem-led service routing

Representative implementation pattern · private source protected

The platform routes a customer's stated problem to a focused solution path. This keeps navigation and intake centered on the need rather than technical product names.

type BusinessNeed =
  | "repetitive-work"
  | "customer-communication"
  | "website-management"
  | "custom-application";

const solutionRoutes: Record<BusinessNeed, string> = {
  "repetitive-work": "/solutions/workflow-automation",
  "customer-communication": "/solutions/ai-systems",
  "website-management": "/solutions/websites-cms",
  "custom-application": "/products/custom-software"
};

export function routeForNeed(need: BusinessNeed) {
  return {
    href: solutionRoutes[need],
    intakeContext: { need, source: "solution-finder" }
  };
}
  • Creates a single customer-facing platform for multiple software and AI service lines.
  • Clarifies the path from business problem to the appropriate solution and intake flow.
  • Supports customer accounts, payments, content, and administrative workflows.
  • Provides reusable architecture for contractor and automotive CMS products.
  • Demonstrates end-to-end ownership from positioning through production deployment.

Source remains private to protect business logic, credentials, customer information, and proprietary workflows.