Ryan Jones

Selected projects

Things I’ve built.

Products across finance, pet care, education and local commerce. My work brings together product thinking, AI and software development.

Sombra

Production core · broader R&D

AI file notes and document workflows for financial advisers. Co-founder and technical product lead.

About Sombra

The product

Sombra turns fragmented meeting data and firm knowledge into reviewable file notes, client intelligence and compliance-aware workflows, then uses adviser corrections to improve future output.

My role

Co-founder and technical product lead. I led product architecture, AI workflow design, application development, integrations, infrastructure and the feedback loop between real adviser behaviour and the product.

What I built

  • Meeting, recording and calendar ingestion with queues, retries and OAuth renewal
  • Structured file-note and document workflows grounded in source material
  • A feedback loop that measures edits and assembles quality-gated examples
  • Production access controls plus broader agent, guardrail and approval prototypes

Technical decisions

Learning from real corrections. Section-level edit metrics, anonymised before-and-after examples and user style profiles turn practitioner review into a controlled improvement loop.

Multi-tenant trust boundaries. Organisation context, role enforcement, governed data access, throttling and traceable activity keep sensitive workflows separated and inspectable.

Broader agent-system R&D. Prototypes explore sequenced and parallel specialist agents, cost tracking, PII handling, persisted findings, output checks and failure fallbacks beyond the production file-note core.

Tend

Built platform · active validation

Pet health records, bookings and day-to-day tools for pet-care businesses.

About Tend

The product

Tend connects an owner-controlled pet health passport with booking readiness and day-to-day operations for kennels, daycare, groomers and other pet-service businesses.

My role

I drove the product model, consumer and business experiences, shared architecture, booking and readiness logic, payments, permissions, AI records assistant, analytics and the go-to-market operating system around the product.

What I built

  • Consumer web and mobile apps, a provider dashboard, administration and a shared API
  • Source-backed document extraction with confidence and human-confirmation states
  • Scoped, expiring and revocable sharing between an owner and a business
  • Bookings, capacity, waitlists, care tasks, invoices, payments and reminders

Technical decisions

Portable records without lost control. Random sharing tokens, explicit data scopes, expiry, revocation, ownership checks and source-document hashes let the record travel without becoming public or permanent.

Policy-based booking readiness. Required and recommended health items produce a clear verdict for each service, and active bookings can be re-evaluated when the underlying records change.

A connected facility operating model. Tenants, venues, staff, rooms, capacity, waitlists, Stripe payments, care tasks and reports remain connected as a booking moves through the business.

Stories Alive

Working product platform

AI tools that help teachers create stories, songs, videos and classroom resources.

About Stories Alive

The product

Stories Alive turns one teaching topic into a coordinated classroom project—storybooks, songs, animated videos, worksheets, presentations and lesson plans—with a guided assistant helping teachers shape and revise the work.

My role

I shaped the teacher product, multimodal generation architecture and creative workflow, then connected the application, background processing, GPU integration prototype, curriculum controls and media review experience.

What I built

  • Connected workflows for stories, songs, videos, worksheets, presentations and lessons
  • A multimodal pipeline across planning, images, music, voice, lip-sync and assembly
  • Lucy, a streaming assistant that can extract structured product actions
  • Curriculum provenance, quotas, cost caps and a ComfyUI GPU-worker prototype

Technical decisions

Character and scene continuity. Role-labelled reference views, film planning and automated clip review protect identity, action, visual style and pacing across many separate model calls.

Resumable, efficient production. Idempotent jobs, partial-progress streaming and a tested low-memory FFmpeg path are designed to keep long projects moving without duplicating expensive work or exhausting a worker.

Curriculum and cost boundaries. Pinned curriculum sources, rights approval, immutable market policies, per-output quotas and account caps constrain what the system can generate before spend begins.

Agent Layer

Personal MVP · review pending

Encrypted personal health data that people can share with their own AI agents.

About Agent Layer

The product

Agent Layer is a personal health-data MVP exploring end-to-end encrypted context: a cloud API stores ciphertext and limited routing metadata while a local MCP layer holds the keys and exposes selected context to a user's agents.

My role

I led the product and system architecture across the vault, cryptographic package, sync model, API, mobile and web clients, and the local agent-facing MCP layer.

What I built

  • A ciphertext API with limited routing metadata and schema-versioned encrypted chunks
  • A local MCP daemon that holds keys, decrypts and merges context
  • A portable cryptographic core for mobile, web and agent runtimes
  • Recovery, relay and sync primitives designed to fail closed

Technical decisions

Cryptographic key and recovery model. The MVP implements domain-separated keys, authenticated encryption, BIP39 recovery and sealed boxes while keeping independent security review as a launch gate.

Encrypted sync model. Monotonic change feeds, canonical headers, merge-on-write and tombstone rules are designed to preserve consistency for the current MVP without asking the server to inspect contents.

Portable agent access. Shared crypto and schema packages support an Expo app, web console, API and local MCP service without creating incompatible security formats.

Naborra

Active development

Local discovery and delivery tools connecting independent businesses, customers and drivers.

About Naborra

The product

Naborra brings local business discovery and a merchant-first delivery network together. Customers can explore nearby businesses, while the wider platform connects ordering, merchant operations and trusted local drivers.

My role

I’m building the product and its connected customer, merchant, driver and operations experiences, including the shared architecture, discovery workflows and delivery systems.

What I built

  • Customer discovery experiences and business listing review tools
  • Business claim workflows and listing publication controls
  • Customer ordering, merchant and driver application surfaces
  • A shared API for orders, dispatch, tracking and operational workflows

Technical decisions

Reliable business information. Imported listings pass through review and publication steps so business details, opening hours and imagery can be checked before reaching customers.

Coordinating multiple roles. Customer, merchant, driver and platform operations experiences share an underlying model while keeping each role focused on its own information and actions.

Delivery state and recovery. Order state, driver assignment, tracking and exception handling need to stay consistent across applications, including when a connection or background job fails.

Website Factory

Live internal product

An internal tool for researching, building and publishing business websites.

About Website Factory

The product

Website Factory turns a business URL into a researched, fact-checked and conversion-focused new website, visually reviews the result, publishes it and manages the human-approved outreach around it.

My role

I designed and built the internal product, staged AI workflow, preview and correction loop, durable queue, campaign operations, AWS publishing and the commercial service around it.

What I built

  • A four-stage workflow from research and grading through design and implementation
  • Fact-integrity controls, SEO/GEO foundations and screenshot-led visual QA
  • A durable job queue with provider orchestration, retries and restart recovery
  • Campaign experiments, guarded outreach and automated AWS publishing

Technical decisions

Quality without invented claims. The system carries real services, brand assets and source facts into generation, then validates artifacts and uses new screenshots to correct the finished experience.

Resilient multi-model production. Stage-specific models, timeouts, logs, process cleanup, priority lanes and lost-process recovery keep long-running creative jobs inspectable and resumable.

Responsible outreach operations. Inbound deduplication, reply classification, unsubscribe handling, send caps, cooldowns and do-not-contact enforcement sit inside the same product as delivery.

Have something in mind?

Tell me what you’re working on.

Let’s talk on LinkedIn