Skip to project library
Key Builds AI

Built by Key Scales / Selected internal builds

Useful AI.
Visible proof.

Turn a repetitive handoff into a workflow you can trust, inspect, and recover.

Discuss your workflow
01 Capture the work02 Keep review in reach03 Verify the result

Selected internal builds and examples. Dated evidence. Clear limits. No invented client results.

The project library

Built with a clear finish line.

Selected applications, workflows and guides.
Evidence and acceptance limits stay visible.

Published componentAcceptance in progressGuide or example

01 / Resources

Published component

The guide a tutorial
actually promised.

A public resource hub that connects useful explanations to matching guides and downloads.

RESOURCE PUBLISHING / SIMPLIFIED
BUDGETTEACHCONTEXT
From promise to a useful resource
Guide + download ↓
Explain → Publish → Verify the destination
What is verified

Existing public resource pages and downloadable guides have publication readbacks.

Where the evidence stops

A live page does not prove a visitor downloaded, used or benefited from it.

Explore the resource hub ↗
Owner-built resource systemSource checkpoint: Oct 24–25, 2026

02 / Content operations

Published outputs · partial

Approved media.
A traceable release.

A content workflow that keeps preparation, approval, scheduling and publication evidence distinct.

ILLUSTRATIVE RELEASE MAP
01Prepare

Exact asset and copy

02Review

Owner approval

03Schedule

Saved placement

04Verify

Published-result readback

What is verified

Published outputs and saved release receipts exist in the established workflow.

Where the evidence stops

Recurring end-to-end operation and some status integrations remain incomplete. No unattended production claim.

Internal content workflowSource checkpoint: Oct 24–25, 2026

03 / Ask Key

Live app · acceptance open

Make the next action
easier to see.

An owner-built app that brings goals, tasks and calendar planning into one working product.

ILLUSTRATIVE VIEW / EXAMPLE TASKS
KAsk KeyPlanning
Example goalImprove the customer handoff
Draft the onboarding guideNext action
Next
Review the weekly prioritiesPlanning task
Review

A simplified explanation, not a live application screenshot.

What is verified

The application exists with goals, tasks and planning interfaces.

Where the evidence stops

Calendar alignment, real-user OAuth and notification acceptance remain open. This is not full-system acceptance.

Owner-built applicationSource checkpoint: Oct 25, 2026

04 / Newsletter

Configuration published

Invite people in.
Preserve their choice.

Published signup configuration and controlled contact recovery, with consent and duplicate checks kept visible.

SIGNUP CONFIGURATION / SIMPLIFIED
Explicit newsletter consentConsent required for enrollment.
Published
configurationRecovery
readback

This diagram is not a live signup or delivery receipt.

What is verified

Published newsletter configuration and a duplicate-free recovery receipt are retained.

Where the evidence stops

The live signup, welcome and suppression test still requires an approved consented test identity.

Internal audience onboardingSource checkpoint: Oct 24–25, 2026

05 / Resource fulfillment

Live configuration · test pending

The right request.
The matching guide.

Post-specific keyword flows connect a published tutorial to the resource its audience asked for.

ILLUSTRATIVE POST-SPECIFIC FLOW
Specific published postComment SILENCEFrom inquiry to follow-up draft
SILENCEMatching guide

No recipient conversation or delivered-message state is shown.

What is verified

Two exact-post resource configurations were verified live on Instagram and Facebook.

Where the evidence stops

Actual recipient delivery and negative keyword/post tests remain unverified. Live configuration is not delivery acceptance.

Internal resource delivery flowSource checkpoint: Oct 24, 2026

06 / Documents

Public guide · example workflow

Extract the details.
Check the source.

A published bill-extraction guide explains how to turn a document into structured information that a person can check.

ILLUSTRATIVE EXAMPLE / NO REAL BILL
EXAMPLEDocument
Structured resultItemAmountDue date
↶ Compare each field with the original
What is verified

The BUDGET guide supplement and its downloadable document are published.

Where the evidence stops

This guide does not establish a deployed extraction service or real customer outcomes. No private document is shown.

Read the BUDGET guide ↗
Owner-authored guide and exampleSource checkpoint: Oct 24, 2026

Build 01 / Lead operations

Internal implementation

A lead pipeline
with brakes built in.

Move eligible records forward without losing track of the ones that need a person.

The implementation recovered blocked imports, reconciled the source records, and verified the provider receipt.

145
records reconciled
60
eligible imports verified
0
duplicates at receipt
RECORDED EXAMPLESilent walkthrough · English captions
Purpose-built simulation with synthetic Example data. It explains the controls; it is separate from the real implementation evidence below.
Read the walkthrough transcript
  1. Review three synthetic Example records. One is eligible, one lacks permission, and one repeats an existing address.
  2. Run qualification. The eligible record is ready. The missing-permission record is held. The repeated address is blocked.
  3. Import the ready record into the local example ledger, then repeat the import. The imported count stays at one.

No outreach is sent. The example ledger exists only inside this recording.

Implementation evidence / Oct 24, 2026

Imports verified. Outcomes still open.

A 145-record reconciliation led to 60 eligible imports verified by provider readback. The verification receipt showed zero duplicates.

Read the shareable evidence summary ↓

Build 02 / Workflow reliability

Internal implementation

Repair the workflow.
Then prove it runs.

Make scheduled work dependable, with a visible path back when a run fails.

Four affected workflow functions were restored and completed natural runs after the repair.

311
API tests passed
4 / 4
restored functions ran naturally
672 → 108
scheduled checks per week
RECORDED EXAMPLESilent walkthrough · English captions
Purpose-built simulation with synthetic Example data. It explains the controls; it is separate from the real implementation evidence below.
Read the walkthrough transcript
  1. Advance an example clock to a scheduled run. A simulated dependency failure leaves the job in a visible failed state.
  2. Repair the example dependency. Advance to the next scheduled check and observe successful recovery.
  3. Read the local receipt. The output is written once. Repeating the same run is held by the duplicate guard.

The clock, dependency, work and receipt are simulated. No real user reminder or external workflow is triggered.

Implementation evidence / Oct 25, 2026

Tests, release, then natural runs.

The repair passed 311 API tests. Four restored functions completed natural runs. A live security release was verified.

Before672 / week
After108 / week

564 fewer scheduled checks per week. This is a configuration-level reduction, not measured dollar savings or staff hours.

Work together

One workflow.
A testable finish line.

Bring a repetitive handoff. We define success before expanding the build.

01 / Diagnose

Find the friction.

Map the trigger, systems, owner and exceptions. Establish the baseline.

02 / Build

Keep the scope clear.

Build a bounded pilot with review points, permissions and failure paths.

03 / Verify

Check the real run.

Compare results to acceptance criteria. Document operation and recovery.

Home servicesInquiry qualification, estimate follow-up and office handoffs.

Property managementMaintenance intake, routing and owner status reporting.

Proposed applications, not completed client engagements.

Tell me about your workflow