TechAppForce

TAFI, said “Taffy”

AI-assisted application building with a confirmation step.

TAFI reads your app, proposes a plan and previews every change. Nothing is applied until you confirm.

Book a TAFI demoTry the change plan
  1. Clarifying questionsWho approves leave? Do half days count?
    Answered
  2. RequirementsLeave requests, balances, manager approval
    Approved by you
  3. BlueprintEntities, screens, lifecycle and workflows
    Approved by you
  4. Build planEvery change TAFI will make, in order
    Waiting for you
Illustration. Nothing is built until you approve the plan.

The problem

AI can write the code. But who maintains it?

Prompt-first builders are quick to a first screen. The trouble starts later, in code nobody on the team owns.

A product owner thinking over a step-by-step plan on a laptop, beside a screen showing a checklist with green ticks and a confirm button

Prompt-first AI builder

  1. Promptquick to a first screen
  2. A pile of one-off code
  3. Changes reported but never made
  4. Credits spent on retries
  5. Code nobody on the team wrote or can maintain

TAFI

  1. Your request
  2. Stages, each stopping for your decision
  3. Configuration in the same app model as TAF Studio
  4. Every object, screen and workflow can be read and changed
  5. Released like any change your team makes
Illustration.

How it works

Preview. Confirm. Apply. Under your name.

Confirmation is enforced by the platform's tool gateway, not left to the AI to remember.

You ask

Add a vendor approval: procurement, then finance.

TAFI previewsDry run. Nothing written.
You confirm
Applied, under your name
By
you@yourcompany.example
Through
TAFI, Agent mode
Check
Read back: 3 of 3 landed
Your sign-in, your permissions Ask reads only Plan writes nothing Agent writes after you confirm
Illustration.

Try it

AI does not silently change your application.

This is the shape of every TAFI change. Review the plan, then confirm and apply it.

TAFI AskPlanAgent
Create a vendor approval process. New vendors need procurement, then finance, before they can be used.
I checked the app: there is no Vendor entity yet, and a Procurement role exists. I will propose the changes below as a plan. Nothing is written until you confirm.
kb_search "approval process" read
taf_describe_entity Vendor read
The plan is ready on the right. Review the changes, then confirm to apply them to Development.
Change planPreview → Confirm → Apply

Request

Create vendor approval process

Plan

  • Create Vendor entity
  • Add approval lifecycle
  • Configure approvers: procurement, then finance
  • Add notification to the requester
  • Add vendor approval screen

Changes

4 metadata changes, applied to Development

Waiting for your confirmation.

What you get

Configuration in your app, not code in a black box.

Whatever TAFI builds is ordinary TechAppForce configuration your team can read, change and release.

  • The same app model

    More
    Entities, fields, queries, screens, lifecycles, workflows, permissions and menus, stored exactly as if a developer had built them by hand.

  • Reviewed in TAF Studio

    More
    Open anything TAFI created in its Studio designer. Read it, change it, run its validation checks or delete it. Your developers stay in charge of the app.

  • Released like any change

    More
    TAFI builds in development. Its work reaches your customers only through a release you review, with the differences between environments shown line by line.

  • Checked before it reports

    More
    Each build step is checked for the right shape and real identifiers before TAFI moves on. A step that reports an object it never created is rejected.

  • Code where it belongs

    More
    When a rule is too specific for configuration, your developers add a C# script as a record hook or workflow action, or a TypeScript screen extension, in the same app, next to what TAFI built.

  • A record of what changed

    More
    After each turn TAFI lists what it changed, with a link that opens each item in its designer.

Where it runs

Use TAFI where you work. Same checks everywhere.

Built into TAF Studio, and available to Claude Code, Cursor or Codex through a gateway that speaks MCP.

TAFI in TAF StudioAsk, Plan and Agent modes
Claude Codethrough the TechAppForce plugin
Cursor or Codexas an MCP client
TechAppForce tool gateway (MCP)
  • Works as the person who signed in
  • Only what that person's role allows
  • Interactive changes run as a dry run first
  • Nothing is saved until you confirm
  • Each write is read back and checked
Your app in Developmententities, queries, screens, lifecycles, workflows, menus
Application historyevery change recorded under your name
Platform knowledge basethe patterns TAFI builds from
Illustration.

Faster building. Every change still yours to approve.

Bring a real requirement. We run TAFI on it with you, from the first question to live screens in a development environment.

Book a TAFI demoOpen TechAppForceExplore TAF Studio
  1. Bring a real requirement
  2. The first question
  3. Every approval in your hands
  4. Live screens in a development environment
Illustration.