Since 2019, and still small on purpose.

A Salesforce and Heroku consulting partner working out of Jaipur. Seventy-plus projects, fifteen-plus clients, four products of our own. What follows is the part most consultancies leave out — the one rule we build against, the work we turn down to hold it, and how long the engagements actually last.

Founded
2019
Studio
Jaipur, India
Partner
Salesforce Consulting Partner
Projects
70+ for 15+ clients
First reply
Within one working day

Every org we hand back is one your own admin can change without calling us.

One rule, held since 2019

Two people sign the work.

CloudAlgo has two co-founders, and both of them are on the build. Whoever you speak to on the first call is one of the two people who will be in your org, and neither of us has stopped writing Apex.

The two CloudAlgo co-founders, standing together in the office in Jaipur.

Sandeep KumarCo-founder · certified since 2014

Fifteen-plus years in software, based in Jaipur. Holds the architect-track certifications the integration work leans on — integration architecture, and sharing and visibility. Writes apex-lint, and builds OrgVitals.

Integration Architecture Designer2019·Sharing and Visibility Designer2019·Platform App Builder2018·Administrator2014·Force.com Developer2014·Force.com Advanced Developer·Sales Cloud Consultant·Service Cloud Consultant

Vikash AgarwalCo-founder · certified since 2016

Fifteen-plus years in software, also in Jaipur. Holds the mobile solutions architecture certification, and carries the off-platform half of the work — the Airflow data pipelines, and the Java and Node.js services and PostgreSQL underneath them. Writes on Apex and on Salesforce security, and builds OrgVitals and Pledgivo.

Mobile Solutions Architecture Designer2017·Administrator2017·Platform Developer I2016

What we build on

Salesforce·Heroku·MuleSoft·Apex·LWC·SOQL·REST / SOAP APIs·Java·Node.js·PostgreSQL·Airflow·AWS

Four things we will not do, and what each one costs us.

We will not build anything your admin cannot change without us.

Costs us — the change requests

We will not quote before we have been inside the org.

Costs us — a slower first invoice

We will not write Apex where configuration would have held.

Costs us — the billable hours

We will not leave without the handover.

Costs us — the second engagement

How long the work actually lasts.

Five published studies — engagement length

Three of the five closed inside six months. Two are still open — one of them past two years, still shipping against the architecture we put in. Read the five studies →