Solution Engineering

Design Proof of Concept Plans

MeshMesh reads the org and the engagement context, then returns a phased proof-of-concept plan with scope, estimates and a build approach that a solution engineer can approve before any build starts.

20 tasks
Method

How MeshMesh does it

  1. Explores the org to confirm what is already enabled and available, such as Agentforce, the relevant objects and Named Credentials.
  2. Researches the relevant Salesforce documentation.
  3. Writes an alignment brief and asks clarifying questions about org scope, the external API and whether to include Data 360.
  4. Produces a phased plan. Plans can include effort estimates, architecture diagrams, custom object schemas, Apex service specs, Agent Script authoring, permissions, testing and optional paths.
  5. Pauses for user approval before building anything.
  6. When the build goes ahead, builds the proof of concept across sessions with Apex, Flow and a Heroku app, then writes a product requirements and handoff document that covers the whole build.

The build itself often continues under Design Demo Build Plans.