Service Overview
The all-in-one IDE for Salesforce
Service Overview
The all-in-one IDE for Salesforce
Contents
01
Why Blaze
02
Key Features
03
Case Studies
04
Security
05
Pricing & Setup
© Igness, Inc.
Common Salesforce challenges
Requests for Salesforce keep growing, but
Do these challenges sound familiar?
Not enough people for the backlog
Quality varies by who does the work
Misread requirements lead to rework
Salesforce project leads
Can't keep up with internal requests
Configuration and errors take too long
Work piles up on the one expert
Salesforce admins and developers
© Igness, Inc.
What is Blaze
Blaze

Salesforce development,
all in one app

Blaze is an AI agent for Salesforce admins and developers. Describe what you want in plain language, and it moves the work forward from organizing requirements to configuration, implementation, testing and deployment.

Requirements, design, implementation, testing and release: everything Salesforce development needs, in a single app.

© Igness, Inc.
Stages covered
From requirements to release, Blaze can take on every stage
Requirements
  • Interview to
    clarify needs
  • Write requirements
    with diagrams
Design
  • Investigate the
    current org
  • Compare options,
    set the data model
Build
  • Configure and
    develop Salesforce
  • Apply to the org
    after approval
Test
  • Write and run
    test classes
  • Check screens
    in a browser
Release
  • Review diffs and
    deploy to production
  • Track changes
    and roll back
© Igness, Inc.
How Blaze works
Blaze turns your instructions into work in your Salesforce org
You
Auto-create an order
when a deal is won
Requirements, meeting notes, goals
Connected Salesforce orgs
✓Dev sandbox
Staging
Production
Changes go only to the org you choose
SalesforceDev sandboxTarget Salesforce org
AI models
BlazeBlazer 1ClaudeOpenAI
Connected apps
SlackAtlassianGitHubGoogle DriveBacklogNotionMicrosoft Teamskintone70+ more
Request
Apply
Read
© Igness, Inc.
What Blaze can do
From objects to Agentforce, all your Salesforce work in Blaze
Blaze

Ask with text, images, Word, PowerPoint or PDF

Objects, fields, page layouts
MCPConnects to 70+ apps
SlackMicrosoft TeamsNotionAtlassianGitHubGoogle DriveGmailBoxBacklogkintonefreeeHubSpotMiroCanvaZapier
Agentforce

Build topics
and actions,
then test them

Flows

Approvals too

Records

No SOQL needed

Permissions

Sharing rules too

>_
Apex & LWC

Test classes generated too

Browser control

Checks UI behavior

Reports

Dashboards too

Canvas

Share by URL

Apps

Apps and tabs

Org connectionsUnlimited

Prod & sandbox

Choose the latest LLMs
Blazer 1ClaudeOpenAI
© Igness, Inc.
01
Why Blaze
01
Why Blaze
Value
What changes with Blaze
1

Requirements to release, all in Blaze

Organize requirements, design, build, test and deploy in one continuous conversation. Context carries over from stage to stage.

2

Connect directly to your org, then apply and test

Blaze reads the latest metadata from the connected org before changing it, then applies the changes. If a deployment fails, it finds the cause and fixes it.

3

Approvals and change tracking you can trust

Blaze asks for confirmation before anything that changes your org, records every change and can roll it back. Deployments to production ask for approval with the target org name shown.

© Igness, Inc.
Before and after
Salesforce development still involves manual work at every stage
Requirements to release, all in Blaze
Requirements
Design
Build
Test
Release
Before
Start building on vague
needs and redo work
Check existing settings
and impact by hand
Switch between setup
screens and code
Test screens by hand
after every fix
Find differences from
production by hand
After
Requirements ModeAnswer questions to get
a requirements document
Org investigationReads metadata and
shows the impact
Build by chatAsk in plain language
and it's applied
Browser testingBlaze checks
screen behavior
Change managementReview diffs,
deploy and roll back
© Igness, Inc.
Why teams choose Blaze
Everything Salesforce development needs is built in

Roll back Salesforce changes

Changes to Salesforce are recorded, so you can return to an earlier state whenever needed and experiment safely

Deploy and test in one place

From deploying to the org to running tests, the work continues in a single app

Diagram requirements and designs

Answer the questions and you get a requirements document with diagrams, making it easy to align with stakeholders

© Igness, Inc.
02
Key Features
02
Key Features
Requirements and documentation
Requirements
Design
Build
Test
Release
Describe what you want,
Blaze interviews you and
writes the requirements
POINT 01

Just answer to turn needs into Salesforce requirements

Blaze asks about the business context, stakeholders, must-have and optional requirements, and constraints, one at a time.

POINT 02

Business flows and ER diagrams, drawn for you

Business flows, ER diagrams and state transitions are produced as real diagrams.

POINT 03

Ready to use as a deliverable

Export to PDF, Word or Markdown. Your org is not touched during this stage.

© Igness, Inc.
Implementation design
Requirements
Design
Build
Test
Release
Investigates your org,
then proposes a data model
POINT 01

Automatically checks your current org

Reads existing objects, fields and automation to find what can be reused first.

POINT 02

Choose from multiple approaches

Compare options such as using standard objects or building custom ones, and agree on a direction.

POINT 03

Data model, screens and validation rules

ER diagrams, page layouts, validation rules and state transitions are decided before anything is built.

© Igness, Inc.

Sign up to see the rest of this deck.

Sign up to keep reading
Org investigation and health check
Requirements
Design
Build
Test
Release
Find unused configuration
and optimize costs
POINT 01

Identify unused objects and fields

POINT 02

Identify unneeded licenses and features

POINT 03

Summarize findings in a report

/health-check summarizes unused fields, flows and licenses, plus Lightning migration readiness, in a report.

© Igness, Inc.

Sign up to see the rest of this deck.

Sign up to keep reading
Supported Salesforce products
Requirements
Design
Build
Test
Release
From core Salesforce to Account Engagement and Data Cloud
Core Salesforce configuration and development
Sales Cloud &
Service Cloud

Objects, fields,
permissions,
records

Flows &
approval processes

Build, fix,
debug errors

Apex & LWC

Classes &
test classes

Agentforce

Topics &
actions

OmniStudio

OmniScript &
FlexCard

Reports &
dashboards

Custom
report types

Data migration

Bulk create and
update via CSV

SlackSlack

Read and post
to channels

Key operations, with setup in advance
Account Engagement
Email templatesList emailsProspectsListsForm handlers
Requires an external client app and a business unit ID. Completion actions and automation rules are set up in the UI.
Data Cloud
Explore dataQueriesBuild support
Create operations require setup in your environment in advance.
© Igness, Inc.

Sign up to see the rest of this deck.

Sign up to keep reading
Approval Mode
Requirements
Design
Build
Test
Release
Approval Mode lets AI
work safely in production
POINT 01

Choose Allow, Always allow or Deny

Blaze stops right before metadata changes, data updates and deployments so you can decide on the spot.

POINT 02

Production approvals show the org name

Deployments to production and data deletion ask for approval with the target org name on screen.

POINT 03

Switch it from the input box

Turn Approval Mode on or off with a toggle in the input box menu.

Confirmation before deploying to productionApproval Mode toggle
© Igness, Inc.

Sign up to see the rest of this deck.

Sign up to keep reading
Objects, fields and permissions
Requirements
Design
Build
Test
Release
Objects, fields, permissions:
just ask in plain language
POINT 01

Proposes changes that fit your org

Checks existing objects and fields before proposing changes.

POINT 02

Page layouts and apps too

Page layouts, Lightning apps, tabs and navigation are set up through chat.

POINT 03

Profiles, permission sets and sharing rules

Even complex access settings are handled entirely in chat.

© Igness, Inc.

Sign up to see the rest of this deck.

Sign up to keep reading
Flows
Requirements
Design
Build
Test
Release
Build flows and fix errors,
all through chat
POINT 01

Build flows and approval processes

Describe the conditions and steps, and Blaze builds the flow or approval process.

POINT 02

Fix errors in existing flows

Blaze finds the cause of an error, fixes it and confirms it works.

POINT 03

Follows flow best practices

Changes follow Salesforce conventions, such as deactivating flows instead of deleting them.

© Igness, Inc.

Sign up to see the rest of this deck.

Sign up to keep reading
Apex & LWC
Requirements
Design
Build
Test
Release
Apex and LWC,
test classes included
POINT 01

Write classes and triggers

Writes Apex classes and triggers from your requirements.

POINT 02

Lightning components too

Builds LWCs and lets you check the result right away in a live preview.

POINT 03

Test classes, automatically

Also writes Apex test classes and runs them in your org.

© Igness, Inc.

Sign up to see the rest of this deck.

Sign up to keep reading
Agentforce
Requirements
Design
Build
Test
Release
Build Agentforce agents by chat
and test them inside Blaze
POINT 01

Create topics, actions and instructions

Create and edit agent settings through chat.

POINT 02

Test behavior on the spot

Talk to the agent from inside Blaze to check its responses and actions.

POINT 03

Connect to Salesforce data

Prepare flow and Apex actions in the same conversation.

© Igness, Inc.

Sign up to see the rest of this deck.

Sign up to keep reading
Canvas
Requirements
Design
Build
Test
Release
Analyze data with AI
and share it as a dashboard
POINT 01

Ask your question in chat

Blaze retrieves Salesforce data and analyzes it as instructed.

POINT 02

Review results in charts and tables

Results are compiled into a dashboard you can review and edit on the canvas.

POINT 03

Share results with stakeholders

Share the dashboard through a password-protected URL.

© Igness, Inc.

Sign up to see the rest of this deck.

Sign up to keep reading
Browser testing
Requirements
Design
Build
Test
Release
Blaze tests behavior
on real screens
POINT 01

Operates a browser inside the app

Blaze reads the screen, clicks and types, and checks that everything works as intended.

POINT 02

Save tests and run them again

Steps are saved as tests you can rerun, edit and share across your organization.

POINT 03

Regression and acceptance testing

After a change, confirm that existing operations still work.

© Igness, Inc.

Sign up to see the rest of this deck.

Sign up to keep reading
Deployment and change management
Requirements
Design
Build
Test
Release
Version-control your changes
and roll back to any point
POINT 01

Deploy with a full diff

Review the differences between sandbox and production as you deploy, with automatic post-deployment checks.

POINT 02

Roll back in one click

Blaze records its changes and checks that a rollback can be applied before reverting. No Git installation needed.

POINT 03

Push and pull with GitHub

If your team uses Git, push and pull to GitHub from change management.

© Igness, Inc.

Sign up to see the rest of this deck.

Sign up to keep reading
Team sharing
Share Skills and prompts with your team
POINT 01

Share in one click

Click “Share to library” in Blaze settings to add it to your organization's library.

POINT 02

Add to your own Blaze in one click

Members just click “Add to Blaze” in the library. Skills are ready to use as slash commands right away.

POINT 03

Version history with rollback

Records who changed what and when. Compare versions and restore an earlier one.

Library in the admin console“Share to library” in Blaze
© Igness, Inc.

Sign up to see the rest of this deck.

Sign up to keep reading
Usage visibility
See who used how much, and in which org, from the admin console

Usage

Credits by model provider, tokens and conversations

Skill usage

Uses per Skill and the number of members using it

By Salesforce org

Users, conversations and credits per org

By member

Conversations, models and tokens per member

About conversation contentOnly usage records are shown, never conversation content
Skill usage chart
© Igness, Inc.

Sign up to see the rest of this deck.

Sign up to keep reading
AI models
Choose Blazer 1, built for Salesforce, or the latest Claude and OpenAI models
Blaze
Blazer 1

High-performance agent mode built for Salesforce

  • Tuned for Salesforce work
  • Responds quickly to keep work moving
  • Keeps costs down
Claude
Opus 5.5Top tier for complex work
Sonnet 5.5Speed and capability
Haiku 5.5Fast, low cost
OpenAI
GPT-6 AstraTop tier
GPT-6.1 SolLatest flagship
GPT-6 SolPrevious flagship
GPT-6 LunaFast, low cost
GPT-5.6 TerraEveryday development
Data handlingBy default, only models with zero data retention can be selected
© Igness, Inc.

Sign up to see the rest of this deck.

Sign up to keep reading
Connected apps (MCP)
Connect to 70+ apps just by signing in

Development

GitHubHerokuGitLabPostmanSupabaseNeonPrismaNetlifyCloudflareBuildkiteSemgrepSocketJamContext7Microsoft LearnExaHugging Face

Docs & files

Google DriveGoogle SheetsGoogle DocsGoogle SlidesMicrosoft OneDriveNotionAirtableDropboxesaCodaGuruBoxEgnyte

Communication

SlackGmailGoogle CalendarMicrosoft Outlook (Mail)Microsoft Outlook (Calendar)Microsoft TeamsLINE WORKSJicooFireflies.aiGranola

Accounting

freeeMoney Forward Cloud AccountingStripePayPalSquarePlaidMercuryRampAirwallex

Projects

AtlassianBacklogkintoneLinearClickUpmonday.comTodoist

Design

CanvaMiroLucidWebflowWixSanityCloudinary

Monitoring

SentryNew RelicGrafanaHoneycombPostHogAmplitude

Sales & support

IntercomAttioCloseKlaviyoJotformHubSpot

Automation

ZapierMake
Blaze “Connections” settings
Apps not listed can be connected
by adding an MCP server
© Igness, Inc.

Sign up to see the rest of this deck.

Sign up to keep reading
More features
Extend your work

Skills and custom prompts

Turn routine work into Skills, and inject instructions such as development standards automatically every time.

Subagents

Split complex work across multiple subagents running in parallel.

Search panel

Search conversations, settings, tests, canvases and files in one place.

Image generation

Generate images for HTML emails in Account Engagement and MC Next.

Use it anywhere

Multiple org connections

Switch between production, sandboxes, scratch orgs and Developer Edition.

Launcher

Open a small input box with a shortcut and ask from any screen.

Blaze CLI

Use Blaze from the terminal. Hooks fit it into your own workflow and CI.

© Igness, Inc.

Sign up to see the rest of this deck.

Sign up to keep reading
03
Case Studies

Sign up to see the rest of this deck.

Sign up to keep reading
03
Case Studies

Sign up to see the rest of this deck.

Sign up to keep reading
Customers
In-house Salesforce teams and partners build with Blaze
Members
LegalOn Technologies
Rhizome
Surpass
Atoms
Sunbit
toBe Marketing
Kenbundo
SINKEN STYLE
TerraSky Technologies
IPS
Quartet Communications
LegalOn Technologies, Inc.With no prompt setup, first answers met80–90% of expectations
Rhizome Co., Ltd.Complex flow and screens during a layover,released in 1.5 hours
Surpass Co., Ltd.Requests that used to take 1–2 weekshandled in 2–3 hours
© Igness, Inc.

Sign up to see the rest of this deck.

Sign up to keep reading
Maintenance and weekly releases
LegalOn Technologies hands weekly releases to Blaze
and shifts time from maintenance to proactive development
LegalOn Technologies, Inc.
CompanyLegalOn Technologies, Inc.
IndustryLegal tech
Challenge
  • As the organization grew, development came to depend on individuals, and standardizing processes and quality became a challenge
  • Weekly releases stretched development resources, and hiring the right people was hard
Why Blaze
  • Deep understanding of Salesforce. With no prompt setup, first answers met 80–90% of expectations
  • Streamlines not only requirements but releases too
Results
  • Small fixes to existing flows and picklist changes go from requirements to deployment with Blaze
  • Used for task breakdown, brainstorming and implementation even on 2–3 week projects
  • Instead of losing time to small tasks, the team can focus on improving the environment and larger projects
© Igness, Inc.

Sign up to see the rest of this deck.

Sign up to keep reading
Self-built by non-engineers
Rhizome completed its Salesforce build and data migration
in-house, without an engineer
Rhizome Co., Ltd.
CompanyRhizome Co., Ltd.
IndustrySoftware (SaaS for commercial facilities)
Challenge
  • Without an implementation partner, the team was building toward full production on its own
  • A non-engineer sales director led the work and got stuck on Apex and complex flows
Why Blaze
  • Not just hints: it works directly in the live environment
  • Handles a wide range of Salesforce work, from consultation to implementation and data migration
Results
  • During an airport layover, in 1.5 hours, a complex flow and new screens went all the way to release
  • Migrated data from the legacy system, including character encoding conversion and deduplication (extracting 30 unmatched records)
  • Bug investigations and spec checks start with asking Blaze
© Igness, Inc.

Sign up to see the rest of this deck.

Sign up to keep reading
Partner productivity
Surpass's less experienced members, working with Blaze,
handled requests that used to take 1–2 weeks in 2–3 hours
Surpass Co., Ltd.
CompanySurpass Co., Ltd.
IndustrySalesforce implementation and enablement, reskilling
Challenge
  • With junior staff and reskilling graduates, many members had little experience
  • Limited technical knowledge made implementation time-consuming
Why Blaze
  • It works against the customer's actual org, reading even the data inside the specified org
  • When errors occur, it finds the cause, fixes them and finishes the job
Results
  • Production deployments now proceed with every difference identified and checked
  • Built the needed Apex from a 100-field budget-vs-actual Excel sheet in about a day (originally estimated at 2–3 months)
  • Some requests that used to take 1–2 weeks were handled in 2–3 hours
© Igness, Inc.

Sign up to see the rest of this deck.

Sign up to keep reading
04
Security

Sign up to see the rest of this deck.

Sign up to keep reading
04
Security

Sign up to see the rest of this deck.

Sign up to keep reading
Security measures
Because AI works on your Salesforce, data and actions stay under control

Never used for AI training

Data you send to Blaze is never used to train AI models.

Credentials never reach the AI

Salesforce credentials are kept separate from the AI and stored encrypted with OS features.

Japan Region Mode

Use only models hosted in Japan to keep all AI processing within Japan.

Centralized admin control

IP restrictions, permission settings and audit logs let admins govern how Blaze is used.

Dangerous actions stopped automatically

Writes to critical files and similar actions are inspected and blocked before they run.

Separated per org

Keep prompts and data separate for production, sandboxes and each org.

ISMS (ISO/IEC 27001)Preparing for certification
© Igness, Inc.

Sign up to see the rest of this deck.

Sign up to keep reading
Admin controls
Set IP restrictions and keep AI processing in Japan
IP address restriction

Limit access with IP restrictions

Only allowed IP addresses can reach Blaze and the admin console. Use test mode to check access before switching to blocking.

Environment settings

Keep AI processing within Japan

The AI processing that generates answers can also be kept within Japan.

© Igness, Inc.

Sign up to see the rest of this deck.

Sign up to keep reading
AI models and ZDR
Conversations sent to AI are kept neither by the model provider nor by us
Zero Data Retention
ZDR
The model provider does not keep what is sent to an AI model once it has been processed.
POINT 01

Only ZDR-compliant models

Blaze uses only models that support zero data retention. What you send is never used for AI training either.

POINT 02

Our relay doesn't store conversations

Our relay to AI models does not store conversation content. Conversation history stays only on your PC.

POINT 03

Other models need admin approval

Models outside ZDR can be used only when an admin allows them in environment settings. Setting changes are recorded in the audit log.

© Igness, Inc.

Sign up to see the rest of this deck.

Sign up to keep reading
Data handling
Conversations and working files stay on your PC, not on our servers
Stored atRetentionProcessing outside Japan
Conversation contentInstructions, answers, files and Salesforce data read by the AIYour PCNot stored on our serversManaged by you on your PCMay be outside Japan depending on the modelJapan only with domestic models
Salesforce dataMetadata, recordsYour Salesforce orgAlso on your PC while working−Same as conversation content for what is sent to AI
Login credentialsBlaze login, Salesforce authenticationYour PCStored with OS encryptionExpiresNone
Shared outputsPublished canvases, library SkillsOur serversOnly when published or sharedUntil unpublished or deletedNone
UsageModels used, token counts, etc.Our servers365 daysNone
Error informationError details, app versionError monitoring servicePer the service's termsUnited StatesSent only with your consent
© Igness, Inc.

Sign up to see the rest of this deck.

Sign up to keep reading
05
Pricing & Setup

Sign up to see the rest of this deck.

Sign up to keep reading
05
Pricing & Setup

Sign up to see the rest of this deck.

Sign up to keep reading
Pricing plans
Start free, then go Professional for full use
All prices exclude tax.
To try it outFreeFor full useProfessional
Monthly price$0$200 / user
Usage20 conversationsWeekly usage allowanceSet a cap for extra usage
Salesforce org connectionsUnlimitedUnlimited
Support−Email and contact form
Payment−Credit card or bank transfer
© Igness, Inc.

Sign up to see the rest of this deck.

Sign up to keep reading
System requirements
Runs as a desktop app on Windows and Mac
WindowsMac
OSWindows 10 or latermacOS 14.5 (Sonoma) or later
CPUIntel Core i5 / i7 / i9,
or Ryzen 5 / 7 / 9
Apple M1, M2, M3, M4 or M5
Memory8 GB or more (16 GB recommended)8 GB or more (16 GB recommended)
Disk space2 GB or more2 GB or more
Network10 Mbps or faster10 Mbps or faster
© Igness, Inc.

Sign up to see the rest of this deck.

Sign up to keep reading
Getting started
Start delegating Salesforce work on day one
1

Create an account

Sign up with a Google account or email address. You start on the Free plan.

2

Install the app

Download and install the Windows or Mac version.

3

Connect Salesforce

Choose production or a sandbox and log in with your Salesforce account.

4

Start asking

Describe what you want, and Blaze shows a plan and gets to work.

Support

Ask us about training sessions for rolling Blaze out in your company.

© Igness, Inc.

Sign up to see the rest of this deck.

Sign up to keep reading
FAQ: features and operations
QHow much of Salesforce can Blaze handle?

Configuration, development and data work that the Salesforce CLI or APIs can handle. Account Engagement and Data Cloud are also supported with some setup in advance.

QIs it safe to connect a production org?

In Approval Mode, Blaze always stops right before deployments and record updates, and asks for confirmation with the target org name before changing production. You choose which org to change before Blaze runs, so sandbox and production work stay separate.

QHow does team management work?

Your company signs one contract, and admins assign licenses to members. Admins can see who used which model, when and how much.

QWhat about Salesforce login and MFA?

You open the Salesforce login page in a browser and log in with your own account. MFA works as usual. Credentials are stored encrypted on your PC and never passed to the AI.

© Igness, Inc.

Sign up to see the rest of this deck.

Sign up to keep reading
FAQ: pricing and contracts
QIs pricing per user or per org?

Professional is $200 per license per month (excluding tax). There is no limit on how many Salesforce orgs you connect.

QCould heavy use run up a large bill?

When the usage allowance runs out, AI use stops, and no extra charges are added automatically. To keep going, an admin can set a cap for extra usage.

QDo I need a contract with Anthropic or OpenAI?

No. Claude and OpenAI models are included in your Blaze license's usage allowance.

QCan I try it before signing up?

The Free plan includes 20 conversations, with no credit card needed. Connect your Salesforce org and try it on real work.

© Igness, Inc.

Sign up to see the rest of this deck.

Sign up to keep reading
Company profile
Creating the future of work with generative AI and CRM
CompanyIgness, Inc.
AddressWizard Bldg. 402, 1-4-3 Sengen-cho, Nishi-ku, Yokohama, Kanagawa, Japan
FoundedOctober 2024
CEOTakuma Ogura
BusinessConsulting on digital transformation (DX)
Salesforce CRM design, build, operations and adoption support
Planning, development and delivery of generative AI services
Blaze

A desktop AI agent for Salesforce admins and developers

Igness LAMP

LINE Official Account broadcasts and conversations, inside Salesforce

Igness BRAIN

Build AI agents for Salesforce without code

© Igness, Inc.

Sign up to see the rest of this deck.

Sign up to keep reading
Thank you
Contact us
Email
hello@igness.ai
Phone
+81-50-3623-3977Mon–Fri 10–18 JST
© Igness, Inc.

Sign up to see the rest of this deck.

Sign up to keep reading