Skip to main content

Salesforce Custom Development for a consulting company

Published by admin
03 March 2018
Salesforce
Professional Services

Project description 

The main goal of the project was to automate the current Salesforce Sales Cloud account, current business-processes where 95% of Leads are received from the website for the customers that provided ITSM and Help Desk solutions. The client used the Salesforce Classic Instance. It was necessary to solve the problem of manual processing of leads, improve integration with different systems and also improve the quality of services performed.

Goals and tasks 

  • Automatically convert new and existing Cold and Hot Leads to Accounts and Contacts with the use of custom logic and to implement the Qualification Process on Account Level;
  • Cope with the challenges of manual data processing;
  • Design detailed test documentation;
  • Participate in working sessions with end clients for resolving issues.

Project scope 

  • Implementation of the Qualification Process on Account Level;
  • Lead to Account matching and Lead to Account/Contact auto- conversion;
  • Use custom logic to log conversion and qualification processes;
  • Adjusting of the Round Robin Process;
  • Set up basic security and organization configuration – profiles, security settings and permission sets, field-level security, sharing rules;
  • Custom logic implementation to log detailed information about processes of conversion and qualification;
  • Close communication with the Customer in order to understand business processes and requirements for Salesforce set up and customization;
  • Requirements analysis and blueprint preparation;
  • Configuration and custom development according to business requirements.

Result 

  • Implemented the Lead to Account matching and Lead to Account/Contact auto- conversion processes, as a result, the problem with manual processing the lead was resolved;
  • Custom Email Notifications were implemented to have the ability to track exceptions and improve the quality of services performed;
  • Implemented the Qualification Process on Account Level, as a result, the quality of performed services has been improved;
  • Set up Security settings;
  • Fully described test documentation;
  • Prepared Blueprint after requirements analyzing.

Advantages of JET BI 

  • Unique technical expertise and experience in the area of Salesforce solutions development;
  • High quality thanks to the efficient QA processes and the transparent handling of bugs enhancement applications;
  • Bureaucracy minimum;
  • High level of employee motivation.
Start your project now
JET BI TEAM
  • 2 Salesforce Developers
  • 1 Business Analyst
  • 1 QA Engineer
  • 1 Project Manager
TECHNOLOGIES
  • Standard Force.com functionality
  • Apex Classes and Triggers
  • Git
PROJECT TIMELINE
  • 6 months
image

We have available resources to start working on your project within 5 business days

1 UX Designer

image

1 Admin

image

2 QA engineers

image

1 Consultant

image
Related Articles
All articles
image
Is Salesforce Winning the Public Sector Race?
An analysis of Salesforce's rapid expansion into the U.S. public sector, tracing its path from cautious early government licensing deals in the 2010s through the launch of Government Cloud in 2012, its pivotal role in COVID-19 vaccine rollouts, and its 2025–2026 push into military and intelligence work via Agentforce and Missionforce. The piece covers major 2026 contracts — including a $5.6 billion Army deal, a $1.6 billion VA agreement, and Pentagon Impact Level 5 authorization — alongside real-world case studies like California's REAL ID processing and the UK's NHS back-office operations. It also examines the structural obstacles still facing Salesforce and other vendors in government tech: legacy IT systems decades old, outdated federal procurement rules, budget constraints, and organizational caution around AI adoption, plus the competitive pressure from Palantir, Microsoft, and Oracle in the race for public sector AI spending.
28 August 2026
image
Why Your Salesforce Flows Are Agentforce's Biggest Problem
This article argues that the most underestimated risk in Agentforce deployments isn't data quality — it's the automation layer: years of overlapping Flows, Process Builder processes, Apex triggers, and managed package logic that no one has reviewed end-to-end. It explains why AI agents inherit automation complexity without the tribal knowledge human admins carry, why technical debt only becomes visible after an agent hits it in production, and why a clean demo is no indicator of production readiness. The article closes with a concrete, tool-by-tool inventory approach using Flow Trigger Explorer, Salesforce Optimizer, Setup Audit Trail, Apex Debug Logs, Agent Builder, and Health Check — scoped to the specific processes the agent will actually use rather than the whole org.
23 July 2026
image
How to Wire Multiple Salesforce Projects in One Org Without Breaking Everything
This article maps the real integration patterns that emerge when multiple Salesforce projects — both managed packages and unpackaged code — share a single org. It covers four concrete patterns: attaching custom triggers to package-owned objects, calling global members exposed by managed packages, writing directly into another project's objects, and runtime-guarded reads of package data. It then addresses access control for authenticated and guest users, including the Master-Detail wall and the without sharing elevation pattern. The piece closes with eight concrete risks (compile-time dependencies that block uninstall, upgrade coupling, silent cascade failures, access invisible to admins) and six actionable recommendations for keeping cross-project coupling manageable.
08 July 2026