Skip to content
maida's desktop
Back to selected work Live product
EmbarkNow
AI PLATFORM · END-TO-END PRODUCT ENGINEERING

Helping people do the work that matters.

An AI workspace for mission-driven organizations—bringing everyday operations, specialist companions, and human-reviewed decisions into one connected product.

Explore the live product
MY ROLE
End-to-end development
THE SCOPE
Frontend, backend, data & AI systems
BUILT FOR
Nonprofits & faith communities
embarknow / productLIVE PRODUCT
The public experience introduces the product through its purpose: helping communities notice needs and coordinate a response.
01 / THE PROBLEM & MY ROLE

The work is connected. The tools usually aren’t.

For a mission-driven organization, a donor conversation, a volunteer need, and a board decision are parts of the same story. But the work often lives in separate inboxes, spreadsheets, documents, and systems. Recognizing what matters—and deciding what to do next—takes time away from serving people.

EmbarkNow brings those activities into a shared workspace. The challenge was to make a broad AI platform understandable in daily use: surface the right context, prepare useful next steps, and keep people in control of consequential decisions.

WHAT I OWNED

I built the project end to end, connecting the application experience to the APIs, data layer, and agent workflows behind it. My scope covered the public product experience, authenticated workspaces, operational modules, AI companion interfaces, and the systems that route work and track decisions.

19modules in the catalog
4specialized companions
Humanapproval at decision points
02 / INSIDE THE PRODUCT

From scattered signals
to a considered next step.

  1. 01Notice the signal
  2. 02Understand the context
  3. 03Review the recommendation
  4. 04Follow through
01

Start with what needs attention.

The command center gives the organization a daily starting point. Activity from modules is organized into attention items, work in progress, and next actions. A companion sits beside that operating picture, so guidance has a clear relationship to the work on screen.

  • Cross-module activity in one place
  • Visible work-unit usage and balance
  • Recommendations with human decision controls
embarknow / command centerLIVE PRODUCT
One operating view connects attention items, active work, decisions, and a contextual AI companion. Shown in a test workspace.
02

Make a broad platform feel navigable.

The module catalog organizes capabilities across relationships, finance, communications, governance, and AI. Access labels and work-unit filters help users understand which tools they can explore, which are included, and which consume usage. A common navigation system connects the modules without erasing their different jobs.

embarknow / module catalogLIVE PRODUCT
The catalog makes the platform’s breadth discoverable while explaining access and usage before a module is opened.
03

Give every recommendation a place to land.

In Donor Relations, the work is grounded in a weekly plan: task progress, thank-you follow-ups, committed activities, and relationship priorities. The companion remains available beside the workspace. This connects conversation to the specific plan or record the user is working with, instead of making them reconstruct the context elsewhere.

embarknow / weekly workspaceLIVE PRODUCT
The weekly workspace turns planning into visible follow-through. The view is cropped above individual donor records.
04

Specialize the AI—and make its scope visible.

Financial stability, discernment, community development, and fundraising have different contexts. Specialized companions bring those responsibilities into separate roles. The interface shows the selected companion’s module access and estimated work-unit cost, with expanded access represented as a request that needs approval.

  • Role-specific assistance
  • Explicit module access maps
  • Usage previews before requests
embarknow / specialized assistanceLIVE PRODUCT
Specialist companions expose their module scope and estimated usage alongside the guidance interface.
05

Keep the person at the decision point.

A recommendation and an approved action are different states. The Approval Inbox makes that distinction visible across submitted planning revisions and draft communications. Pending, approved, declined, and deferred work stays organized, while reviewers can inspect the material before deciding what should happen next.

embarknow / approval inboxLIVE PRODUCT
Planning revisions and communications move through explicit human decision states. Donor-level records are outside this crop.
03 / UNDER THE SURFACE

A shared foundation.
Specialized intelligence.

The application, conversation layer, agent workers, and operational data work together behind the interface.

embarknow / system architecture4 LAYERS
  1. 01

    Application experience

    React · TypeScript · Vite

    Modular screens and contextual companion panels, with shared navigation, reusable interface components, and client-side data fetching.

  2. 02

    API & conversation layer

    FastAPI · Python

    Typed request handling and conversation endpoints connect the web application to operational and AI workflows.

  3. 03

    Agent execution

    Redis Streams · CrewAI

    Routed requests reach a worker that resolves the relevant module crew, executes its work, and publishes progress and results.

  4. 04

    Shared operational context

    PostgreSQL · asyncpg

    A shared database layer supports application context and execution records, with observability contracts linking work to its tenant and lifecycle.

ReactTypeScriptViteTailwind CSSFastAPIPythonPostgreSQLRedisCrewAI
ENGINEERING DECISION / 01

Reuse the engine; specialize the work.

A pack-based crew factory loads a module’s implementation behind a common execution interface. Operational areas share infrastructure while keeping their own tools, context, and responsibilities.

ENGINEERING DECISION / 02

Keep long-running AI work off the request path.

Redis-backed workers separate agent execution from the web interface. Progress and result events give the application a way to represent work that continues beyond a single request.

ENGINEERING DECISION / 03

Make authority visible in the product.

Approval states, reviewer context, and access maps are part of the interface as well as the backend model. Users can distinguish suggested work from reviewed decisions and understand the scope of a companion’s guidance.

04 / WHAT SHIPPED

A complete platform.
A human at the center.

The result is a live, connected product that spans discovery, daily operations, specialized AI assistance, and human review. The platform brings a 19-module catalog and four specialized companions into a common application experience, with a detailed donor workflow that connects planning to follow-through.

  • Public product experience and authenticated workspaces
  • Command center and discoverable module catalog
  • Contextual companions and specialist director interfaces
  • Donor planning, task progress, and approval workflows
  • Shared API, database, and asynchronous agent infrastructure

Useful AI depends on the workflow around it: the context it receives, the work it produces, and the point where a person makes the decision. EmbarkNow brings those pieces together in the same product.

Screenshots captured from the live application. Account details and individual donor records are excluded from the selected views.

Thoughtful systems. Useful AI. Real work.

Building something ambitious?

Back to all projects
EmbarkNow homepage introducing cooperative AI and the flow from community signals through ethical boundaries to mission response helpers

The public experience introduces the product through its purpose: helping communities notice needs and coordinate a response.

Good things start with hello.

Find me here. Let's make something useful.

More about my experience Résumé