Now planning React + GraphQL and LWC + GraphQL

Plan Salesforce features in

Force1 turns a one-paragraph requirement into a buildable plan grounded in your real org metadata. Approve, edit, or reject every piece — your local Claude Code writes the React or LWC and ships it through SFDX.

Bring your own Salesforce org and Claude Code subscription.

Force1 planner · live

streaming
user

projects · broker-onboarding · BrokerOnboardingWizard

Capitated Bundle wizard plan

awaiting review
RequirementOverviewFeaturesData model3UIGraphQL

New objects

Capitated_Bundle__c
NEW5 fields
Capitated_Association__c
NEW4 fields
Participating_Program__c
NEW3 fields

Relationships

Bundle__c
Account
Assoc__c
Facility
new reused lookup

Capitated_Bundle__c · fields

5 will be created
API nameTypeStatus
Name__cText(80)approved✓ ✗ ✎
Tax_Id__cText(20)approved✓ ✗ ✎
Service_Type__cMultiPicklistedited✓ ✗ ✎
Effective_From__cDateapproved✓ ✗ ✎
Account__cLookup(Account)pending✓ ✗ ✎

Built for Salesforce teams in every vertical

HealthcareFinancial ServicesManufacturingPublic SectorEducationNonprofitRetailTelcoEnergyLogisticsHealthcareFinancial ServicesManufacturingPublic SectorEducationNonprofitRetailTelcoEnergyLogisticsHealthcareFinancial ServicesManufacturingPublic SectorEducationNonprofitRetailTelcoEnergyLogistics
The pitch

For the architects who'd rather ship than scaffold.

Force1 reads your org's actual schema, classes, triggers, and flows — then plans only what fits. No generic boilerplate. No invented fields. No "now go connect this manually" footnotes.

0stacks

React Multi-Framework · LWC · GraphQL UI API. One target per requirement.

0%

Plans grounded in your scanned org metadata.

0boilerplate

No starter-kit fluff. Plans only what your requirement needs.

0click

Plan → review → Claude Code writes → SFDX deploys.

How it works

From a paragraph to a deployed feature

Four steps. Two tools. None of the boilerplate.

Step 01 · Plan

Plans grounded in your real org

Force1 scans your org via SOQL — every customizable object, every custom field, every Apex class and trigger. The planner only references things that actually exist in your schema.

Live schema reference

scanned 2m ago
Account
67 fields
Contact
54 fields
HealthcareFacility
32 fields
Capitated_Bundle__c
NEW5 fields
Capitated_Association__c
NEW4 fields
Step 02 · Review

Approve, edit, or remap before anything is created

Every feature, object, field, UI component, and GraphQL query is its own approve / reject / edit decision. Don't want a new field — remap it to an existing one with one click. Finalize stays disabled until every item is decided.

Plan review

1 pending
Capitated_Bundle__capproved
Capitated_Bundle__c.Status__cedited
BrokerOnboardingWizardpending
queryBundlesapproved
Account.MagicScore__crejected
Step 03 · Preview

Interactive prototypes before you ship

Once the plan is approved, Force1 generates clickable Salesforce-styled HTML prototypes of every UI component — wizards advance, inputs validate, tables sort. Validate the flow with stakeholders before a single component lands in your org.

Interactive prototype

desktoptabletphone
Force1 / OnboardingCreate Capitated Bundle

Step 1 of 3 · Identify the broker

84-1234567
30309
BackNext
Step 04 · Build

React Multi-Framework or LWC. Your call.

Pick the framework that fits the team and the org. Force1's planner adapts component specs and Claude Code writes the right files: .tsx for the React Multi-Framework, or .html / .js / .js-meta.xml LWC bundles. Same plan UX — different output.

Pick once, plan adapts

React + GraphQLRECOMMENDED

.tsx in the Salesforce React Multi-Framework UIBundle. Vite + Tailwind + shadcn primitives. GraphQL UI API for data.

LWC + GraphQLBETA

Lightning Web Components with @wire(graphql) reads, NavigationMixin routing. Deployed straight to force-app/main/default/lwc/.

LWC + Apex + GraphQLBETA

LWC frontend, Apex for transactional logic GraphQL UI API can't express, GraphQL for reads. Plan-level support today.

Apex onlyBETA

Server-side automation — triggers, services, batchables. No UI. Plans Apex stubs with kind, signature, and bulk-safe expectations.

Capabilities

Three steps. One workflow.

Plan in the web. Build with Claude Code in VSCode. Deploy through your own SFDX. Force1 stitches the pieces.

01

Plan

Describe what you want. Force1 plans the data model, GraphQL queries, and UI components — every proposal traceable back to your real schema.

02

Build

Approve the plan and Claude Code writes the code in VSCode — React Multi-Framework or LWC. Your subscription, no per-token bills.

03

Deploy

Build & Deploy Bundle, or push individual LWCs, straight to your scratch org or sandbox via SFDX. No CI dance.

Modes

However you want to start

Three modes for the three ways teams actually scope work.

Single task

I have one thing to build now

Describe a single task — get a focused plan and working code in one sitting. Best for scoped tickets and prototypes.

User stories

I have user stories to build

Paste your full backlog of stories. Force1 groups them, designs the data model once, and proposes screens for every flow.

Discovery · soon

I have a project to plan

Step-by-step discovery with reviews at each stage. For teams scoping a new initiative from scratch.

Stitched together with the tools you already trust

Salesforce CLI
VSCode
Claude Code
Anthropic API
OpenAI
Supabase
Vercel
GraphQL UI API

Stop scaffolding.
Start shipping.

Free during beta. Bring your own Salesforce org and your Claude Code subscription — Force1 handles everything in between.