I’m Ayo Richard Abe, also building as gODtECH. I work where product thinking, software engineering, systems design, AI-assisted development, and execution meet.
I like difficult, messy problems: disconnected workflows, repetitive work, unclear product decisions, infrastructure friction, or ideas that need to become something real enough to test.
|
Discovery, requirements, roadmaps, prioritization, user flows, validation, and delivery. |
Architecture, APIs, data, automation, infrastructure, internal tools, and operational workflows. |
Prototype quickly, prove what works, harden the system, ship, observe, and improve. |
PROBLEM
↓
UNDERSTAND
↓
DESIGN THE PRODUCT + SYSTEM
↓
BUILD → VERIFY → SHIP
↓
EVIDENCE → ITERATION
The portfolio is no longer one big list of experiments. Some products are live and active, while others are deliberately still in building mode.
| Product | What it does | State |
|---|---|---|
| 🏗️ Proqurement | Construction supplier discovery, sourcing, comparison, and market intelligence |  |
| 🛡️ Snare | Repository-focused software supply-chain security scanning | |
| 🏥 OHealth+ | Healthcare workflows, professional tooling, bookings, APIs, and patient access | |
| 🏫 Cyfamod SMS | School management for students, attendance, results, fees, staff, and communication | |
| 🧩 Vettika | Product and collaboration workflow platform | |
| 📣 NanoClick | Campaign operations for task workers and nano-influencer workflows | |
| ♻️ Waste2Light | Renewable-energy, circular-economy, education, and practical innovation platform | |
| ✉️ ABEmail Mail | Managed business email infrastructure around customer-owned domains | |
| 🧠 Lead Engine | Recruitment intelligence for discovering, verifying, and organizing hiring-market data | |
| 🧭 ABE TechLab Operations | Operating system for CRM, research, outreach, content, analytics, GitHub, and AI-assisted operations | |
Live here means shipped or actively operating. It does not mean the product has stopped evolving.
Three public developer systems now form the core of the engineering layer: one orchestrates the work, one scaffolds the project, and one keeps the repository healthy.
Opinionated project scaffolding for production-minded repositories. StackPilot gives developers a deliberate golden path instead of hundreds of arbitrary combinations. Its validated backend paths cover Rust/Axum, Go/Chi, TypeScript/NestJS, Python/FastAPI, Java/Spring Boot, and C#/ASP.NET Core. |
Framework for Orchestrated Reasoning, Governance & Engineering. FORGE sits between human product intent and AI execution so an agent does not jump directly from a request into code. It structures research, product reasoning, architecture, design, engineering, security, verification, and deployment. |
Repository housekeeping and health for developer systems. Steward scans repositories deterministically, reports health findings, verifies trusted external rule packs, and supports conservative maintenance without silently mixing its rules into the products it observes. |
Together they form a deliberate developer-tooling layer: FORGE governs the engineering workflow; StackPilot scaffolds the project; Steward keeps the repository healthy. They remain independent products with clear boundaries and public interfaces.
The rest of the active build queue is intentionally separate from the shipped board.
| Project | Current direction | State |
|---|---|---|
| 🎙️ SAYRR | Voice-first input that turns natural speech into usable text wherever you type |  |
| 🏦 MortgageOps | Mortgage operations, credit, underwriting, servicing, risk, and case management | |
| 🎓 TechTrack | Learning, bootcamps, internships, cohorts, progress, and certificates | |
| ☁️ Cloud Infrastructure Platform | Infrastructure laboratory exploring compute, lifecycle, networking, storage, and control-plane foundations | |
| ♻️ Waste2Work | Workspace operations and time-billing platform direction | |
| 🍽️ Lucid | Legacy restaurant POS and operations experiment retained as part of the product history | |
Build the right thing, build it deliberately, and prove that it works.
I care about the difference between something that looks finished and something that actually works. My default is to reduce uncertainty before adding complexity.
01 Understand the real problem
02 Define the smallest useful product
03 Make architecture and UX decisions explicit
04 Build with real state, not fake behaviour
05 Test security, reliability and failure paths
06 Ship something observable
07 Learn from evidence and iterate
This is also why so much of my work lives around product specifications, architecture, automation, developer experience, validation, and operational systems rather than just interface code.
| Layer | Tools / focus |
|---|---|
| Product | Discovery, requirements, roadmaps, prioritization, delivery, validation, product operations |
| Frontend | TypeScript, JavaScript, React, Next.js, TanStack, Tailwind CSS |
| Backend | Node.js, NestJS, Python, FastAPI, Go, Java, C# |
| Data | PostgreSQL, Supabase, MongoDB, SQLite |
| Infrastructure | Docker, Terraform, AWS, Vercel, GitHub Actions, virtual machines |
| AI systems | AI-assisted development, agent workflows, research, governance, automation, verification |
| Design & collaboration | Figma, product specifications, architecture documents, Git, GitHub |
NOW
├── Continue evolving StackPilot golden paths
├── Keep gODtECH FORGE strong as a reusable engineering intelligence layer
├── Keep gODtECH Steward strong on repository health and maintenance
├── Harden live products and operating systems
├── Continue SAYRR, MortgageOps and TechTrack product development
├── Push developer experience, automation and infrastructure work deeper
└── Keep converting experiments into measurable, usable systems
NEXT
├── Production hardening
├── Better observability and testing
├── Stronger security boundaries
├── More reusable product + engineering patterns
└── More public demos, documentation and independently useful tools
I’m interested in conversations around products, developer systems, AI-assisted engineering, infrastructure, automation, and practical technology.
Ayo Richard Abe · gODtECH
Product × Engineering × Systems