DEV Community

Okeke Chukwudubem
Okeke Chukwudubem

Posted on

One Codebase. Two Products. Here's How I Built Both at Once.

AccessBuild taught me the pattern. AgriMind is applying it. Both are live.

If you've been following my build logs, you know the rhythm.

I was deep into AccessBuild—an AI-powered accessibility audit tool that scores mobile apps from A to F. Day 2 shipped: Supabase integration, UI tree parsing, auto-scanning. The API was live. The scoring engine worked.

Then I paused it.

Not because it failed. Because I saw the pattern.

The Pattern

AccessBuild and AgriMind share the exact same architecture:

  • FastAPI backend
  • Supabase database
  • Google Gemini AI
  • Render hosting
  • API-first design

Every line of code I wrote for AccessBuild's backend was directly reusable for AgriMind. So instead of finishing one and starting the other from scratch, I built the shared foundation once and applied it to both.

What AgriMind Is

AgriMind is an AI-powered farm advisor on WhatsApp. Farmers send text or photos of sick crops and livestock. The AI replies with diagnosis and treatment advice in their own language.

Free for 3 questions. ₦8,000/month for unlimited.

The goal: instant expert advice for farmers anywhere in the world. No app. No internet beyond WhatsApp. Just a conversation.

What I Built

Component Status
FastAPI backend ✅ Live on Render
Supabase database ✅ Connected
Gemini AI brain ✅ Integrated
Paystack payment logic ✅ Built
Meta WhatsApp webhook ✅ Verified
Messages subscription ✅ Active

The backend is live at: agrimind-api-xm7p.onrender.com

The Shared Stack

Component AccessBuild AgriMind
Backend FastAPI FastAPI
Database Supabase Supabase
AI Gemini Gemini
Hosting Render Render
API Design REST REST

Same bones. Different problems.

The Wall I Hit

Meta's test number. It works differently than expected:

  • You can't just message it like a contact
  • You must receive a template first, then reply to that template
  • Only then does the 24-hour conversation window open

I'm still debugging this. The backend is ready. The AI is ready. The only blocker is Meta's sandbox restrictions.

What's Next

  • Get the Meta test flow working end-to-end
  • Register a real WhatsApp Business number
  • Complete Meta business verification
  • Launch AgriMind with real farmers
  • Return to AccessBuild with the same infrastructure

Why I'm Sharing This

Because this is what real building looks like. You pause one thing to finish another. You hit walls that have nothing to do with your code. You keep going.

AccessBuild will be finished. AgriMind is almost there. Both share the same bones.

That's the advantage of building systems, not just projects.

Dexter

Top comments (0)