Question 1

How do you prepare a package for Security Review?

Accepted Answer

Every package is developed from day one against Salesforce’s actual security scanner rules rather than audited at the end. We run Salesforce Code Analyzer continuously during development, run DAST scans before submission, and prepare the Solution Architecture Document the review team asks for. Every package we have worked on has cleared review. If findings come back on a package we built, we remediate them at no additional cost.

Question 2

How does Vertex Infinite compare to large SI agencies?

Accepted Answer

Large agencies carry high minimums, take months to scope, and often hand delivery to a team you never met. Vertex Infinite is a small independent practice: you work directly with the engineer building your package, from first call through to listing, with no agency overhead.

Question 3

Why are client names withheld on your public portfolio?

Accepted Answer

We work under strict mutual NDAs with enterprise software companies, FinTechs, and healthcare organizations. Because their AppExchange packages represent their core commercial intellectual property, we respect their confidentiality. We do not publish their names, and we do not arrange contact between clients.

Question 4

Can you help us build Agentforce AI agents inside our existing managed package?

Accepted Answer

Yes. We specialize in building Agentforce-ready 2GP packages, designing custom Agent Actions in Apex, configuring Prompt Templates grounded in Data 360 records, and establishing Einstein Trust Layer guardrails.

Question 5

Do you work with startups that have never worked with Salesforce before?

Accepted Answer

Yes — teams whose product has never touched Salesforce are a core part of what we do. B2B SaaS companies typically need an AppExchange presence to unlock enterprise sales. We guide you through partner registration, design the packaging architecture, prepare the package for Security Review, and set up the listing.

Question 6

How does the payment process work?

Accepted Answer

Exactly as agreed, and never outside it. Before any work begins we settle the payment schedule with you in writing, alongside the scope and the quote, and payments then follow that agreement. The terms themselves depend on the engagement — a product build, a single change and ongoing support each run differently — so we agree them with you on the call rather than applying one schedule to work that does not fit it.

Severity	What it means	First response	Then
Production down	Installed package unusable in production	Within 1 business day	Worked continuously until a fix or workaround is in place
Major	Core feature broken, no workaround	Within 2 business days	Fix scheduled into the next patch release
Minor	Feature degraded, workaround exists	Within 3 business days	Scheduled into a future release
Question	How-to, configuration, or documentation	Within 3 business days	Answered directly, documentation updated where useful

Support

01Response targets

02What to include

03Escalation

04Security issues