DARRELL JAVAN / TECH PORTFOLIO
Client builds · AOS studio · Personal projects

Tech Builds.
Marketing Systems.
AI Agents.

Darrell Javan Wells. I build the systems that greet customers, move work, and help teams operate.

Explore the systems ↘Open the demos ↗
Visible workflowsDefined agent rolesHuman handoffs
01 / Systems

See how the work moves.

Open a demo or trace a workflow. The maps illustrate the real structure of each build without exposing private records.

Client systems
01 / Client workClient engagement

Industrial client, Dubai

Dubai industrial build

Agent teams built a factory website and a firefighter resource hub. Grok receptionist bots handled greeting, questions, and routing. The work continued into a three-month local AI infrastructure engagement.

What the agents doBuild teams develop the web experiences. Receptionist bots answer and route. Local infrastructure provides the operating layer.

Walkthrough available on request.
Workflow map Illustrated sequence
01Client brief
02Agent teams
03Factory website + resource hub
04Reception + local AI

Two web experiences and an operating layer for the same industrial client. Client identity and business data stay private.

02 / Client workLocal runtime built

Dubai wellness center project

Command Center OS

A multi-agent control room built for the Dubai client’s wellness center project. Operators choose a job and review the result from one dashboard.

What the agents doHelpers load approved knowledge, prepare a plan, do the work, check it, and return a report.

Walkthrough available on request.
Workflow map Illustrated sequence
01Request
02Approved memory
03Plan
04Hermes
05Quality check
06Report

LangGraph coordinates the workflow. A model router selects local models through Ollama. The architecture includes llama3.1:8b for fast operations, qwen3.6 for heavier reasoning, and a GLM/Z.AI lane.

03 / Client workClient systems built

Berlin nonprofit

Eurasia Sportakademie

A website and funnel rebuild connected to Vapi voice agents, QR check-in and scanner, an internal CRM app, and support for Erasmus and funding applications.

What the agents doVoice agents greet and route. Maintenance agents support the app. Other agent work supports research and application preparation.

Open the app and voice demos ↗
Workflow map Illustrated sequence
01Website + voice
02QR check-in
03Internal CRM
04Maintenance + funding support

The check-in app, scanner, CRM, and support workflows serve the nonprofit’s daily operation.

04 / Client workSix agents built

YouTube creator, Denver

Six-Agent Build Suite

A content operations suite built for an up-and-coming YouTuber. Six roles divide prospecting, trend watching, video preparation, publishing, and outreach.

What the agents doEach named role prepares a different part of the content and outreach workflow.

Walkthrough available on request.
Workflow map Illustrated sequence
Lead GenAudience brief↓Prospect list
TikTok TrendsContent signals↓Trend ideas
YouTube FacelessVideo brief↓Video preparation
YouTube UploaderVideo assets↓Upload workflow
Outreach Writer v2Lead context↓Message draft
Instagram PosterContent assets↓Post workflow

The operations board below shows role boundaries. It does not display live client activity.

05 / Client workNewsletter system built

Wellness coach, Los Angeles

The Transmission

A newsletter system behind an aromatherapy coaching product. Research and newsletter work are handled in separate stages.

What the agents doA research agent prepares a digest and preview. A newsletter agent turns the reviewed material into the send.

Walkthrough available on request.
Workflow map Illustrated sequence
01Friday / research
02Digest
03Review
04Sunday / newsletter
05Send

The documented workflow uses Firecrawl and Exa for research, NVIDIA NIM for the digest, and Brevo for email delivery. This panel shows the weekly sequence.

06 / Client workRebuilt and handed off

App migration and rebuild

Proper Pairings app lift

Agents lifted and rebuilt the app, recovered its sound library, restored an independent build path, and fixed the YouTube embeds.

What the agents doBuild work covered migration, asset recovery, integration repairs, and checks of the app’s routes and offline behavior.

Open Proper Pairings ↗
Workflow map Illustrated sequence
01Existing app
02Lift + rebuild
03Media + embeds
04Route + offline checks

The migration handoff records self-hosted audio, direct billing integration, build configuration work, and regression checks.

AOS studio systems
07 / AOS studioPublic catalog

Public app catalog

AOS App Machine

The AOS studio’s collection of apps, websites, tools, and experiments. A place to open the work and see what each build does.

What the agents doAgent-assisted building and testing supports the studio’s delivery work.

Explore the App Machine ↗
Workflow map Illustrated sequence
01Business need
02Build
03Check
04Public app catalog

Explore the catalog for individual apps and live project links.

08 / AOS studioLocal system built

Outreach operations

AOS Universal Outreach Engine

A connected workflow for finding leads, researching them, writing messages, sending, and tracking follow-up.

What the agents doResearch and writing prepare the message. Sending and tracking stages keep the sequence organized.

Walkthrough available on request.
Workflow map Illustrated sequence
01Lead sources
02Research + writing
03Sending lane
04Fallback
05Tracker

Apollo, Google Maps, and Firecrawl feed the research lane. NVIDIA NIM has a Groq fallback. Instantly has a Brevo SMTP fallback. A local CSV records the work.

Personal systems and future projects
09 / Personal systemIn daily use

Daily operation

Personal agent operating system

A multi-agent assistant built and operated with Muse and Codex. Scheduled briefings, watchers, memory, and goals support ongoing work.

What the agents doWatchers check for changes against alert rules. Subagents handle delegated work. Memory and goals keep context across sessions.

Walkthrough available on request.
Workflow map Illustrated sequence
01Schedules + watchers
02Alert rules
03Subagents
04Memory + goals
05Briefing

Only the system structure is shown here. Personal records, alert subjects, and private memory are excluded.

10 / Future personal projectPublic learning preview

Nine-module curriculum

Agent School

A curriculum on building and running agents: foundations, agent anatomy, teams, orchestration, commerce, safety, human judgment, and build labs.

What the agents doThe curriculum teaches how to define roles, connect tools, coordinate teams, and review their work.

Open Agent School ↗
Workflow map Illustrated sequence
01Foundations
02Agent anatomy
03Teams + orchestration
04Judgment + safety
05Build labs

A future personal project with a public learning site.

02 / Demos

Open the work.

Explore the app and watch the voice agent in action.

Interactive app / Fictional demo data

Eurasia operations app

A view of the member, class, attendance, and operations interface. All records in this demo are fictional.

Interactive app demo
Members → Classes → Attendance → Operations
Open the full app ↗
Voice agent / Recorded demonstration

Vapi voice agent demo

Watch a voice agent demonstration. The recording shows the conversational experience.

Voice agent recording
Open the video using the link below.
Watch on Loom ↗
03 / The method

How I build a bot.

Customer support, reception, lead capture, ecommerce, and internal bots that watch, alert, and hand work to a team.

Open the build walkthrough
01 / Method

Intake

Define the job, voice, catalog or services, policies, FAQs, and escalation rules. Know what a good handoff looks like before building.

02 / Method

The brain

Build an instruction sheet and knowledge base from the business’s own facts. Products, shipping, returns, discounts, and services form the answer base.

03 / Method

The connections

Use the tools the business already has. Shopify for product and order data. Klaviyo for capture and flows. Gmail for drafts. Slack for handoffs. CRM and booking tools where needed.

04 / Method

The guardrails

Answers stay inside approved facts. No invented prices, unauthorized refunds, or promises outside its lane. No arguing. Unknowns and exceptions go to a person.

05 / Method

Launch

Test with hard questions, missing facts, policy exceptions, and handoff cases. Check what the customer hears and what the team receives.

06 / Method

Upkeep

Monitor answers and alerts after launch. Update business facts, review handoffs, and tune the system as the operation changes.

Sample configuration / Fictional store / Not a client

Harbor Lane Home Goods

A fictional store with eight products. Choose a customer request to see how a finished build routes the work.

Customer request

Will this lamp work with a dimmer?

System response path

Check the product facts. If dimmer support is not listed, say that and offer a human handoff.

Product question
Will this lamp work with a dimmer?
Check the product facts. If dimmer support is not listed, say that and offer a human handoff.
Order lookup
Where is my order?
Use an approved order lookup after the required identity check. Show only the information needed to answer.
Lead capture
Can you let me know when it is back?
Ask for consent to collect an email and connect the request to the store’s follow-up flow.
Human handoff
Can you refund a damaged item?
Explain the approved process and pass the request to a person. The bot does not issue the refund itself.
04 / Marketing + GTM

From attention to follow-up.

Eurasia’s site and funnels, AOS outreach, and client delivery systems connect the public experience to the work behind it.

01Lead capture
02CRM record
03Email or booking
04Team handoff
05Follow-up

A process map for the work across these builds. Each project uses the parts its business needs.

More client systems
11 / Client build / AOSPublic booking site

Barbershop

Booking and owner operations

A service website with appointment booking and a private owner view for managing the day.

How it worksWorkflow: customers choose a service and available time. The booking is recorded and an email alert is prepared.

Walkthrough available on request.
Workflow map Illustrated sequence
01Service
02Available time
03Booking
04Owner view + alert

The owner can manage appointments and block unavailable times. No customer records are shown in this portfolio.

12 / Client build / AOSSite deployed

Product business

Product proof and ordering

A website and ordering system with a visible product proof, order capture, and a handoff for fulfillment.

How it worksWorkflow: product choices become a proof and order record, then move into the business’s fulfillment process.

Walkthrough available on request.
Workflow map Illustrated sequence
01Product choices
02Visible proof
03Order record
04Fulfillment handoff

The build includes brand assets, site source, an order API, and owner documentation. Delivery metrics are not claimed.

13 / Client build / AOSSite built / booking demo

Yoga business

Service website and booking flow

A website rebuild with classes, booking and shop interfaces, contact capture, and a private website manager.

How it worksWorkflow: visitors explore classes, choose a booking, and reach the business. The owner has an editing interface.

Walkthrough available on request.
Workflow map Illustrated sequence
01Class discovery
02Booking choice
03Contact + follow-up
04Owner updates

The handoff identifies booking and checkout as demo mode pending schedule and payment setup.

05 / Working with me

Build. Check. Operate.

A clear scope, a working build, and a handoff the team can use. White-label available.

01 / IntakeDefine the job
02 / BuildConnect the parts
03 / TestAsk hard questions
04 / LaunchCheck the real flow
05 / UpkeepWatch and tune