Did any teams here successfully transition from Blueprint to a working application or the dev team has to recreate a application manually?
If you used Blueprint primarily as a prototyping tool, how closely did the final implementation align with original blueprint model?
what are the challenges encountered during the process?
I’m working on to create a contact center application, how ever the Pega AI suggested processes never align with my objective; how ever I’m editing the case types according to my requirement, just curious how’s it going at your end!
I’ve worked on a few projects—some currently mid-air in progress and others nearing completion—where teams have successfully transitioned from a Blueprint into a functional application within the platform. While some level of configuration is always necessary (typical example - Decision Rules, Score cards etc. ) post-import to align the application with specific business needs, there had been no need to recreate the application manually from scratch.
In our case, Blueprint has served as far more than just a prototyping tool. It has enabled us to bring the project vision to life much earlier in the lifecycle, significantly streamlining both development effort and requirements gathering.
Regarding your point about AI-suggested case types not aligning with your objectives:
While the initial suggestions may not always hit the mark entirely, they are based on how the problem or objective is articulated in the initial description. Iteratively refining that input—being specific about goals, outcomes, and user personas—can often yield results that are much closer to your intended solution.
In my experience, the generated case types and processes have generally aligned well with the vision provided, and iterative refinement has helped bridge any remaining gaps to reach the desired outcome.
Hope that helps, and would be great to hear how your contact center app progresses!