Example package
HubSpot or Salesforce build
Your CRM set up or reworked around your sales process.
You get
- Pipeline and fields agreed
- Automations built and tested
- Data moved and cleaned
- Team walkthrough
How it works
- 1You describe it
- 2A written scope
- 3Milestones you review
- 4Handover and a 30-day fix window
How we work, step by step · The 30-day fix window in our agreement (section 9)
Sound familiar?
What we hear from businesses before a project like this starts.
- Our CRM has hundreds of fields and nobody trusts the data.
- Deals and contacts are copied by hand between the CRM and our other tools.
- We need a custom object, workflow or report the CRM's settings can't do on their own.
- The freelancer who set up our CRM has gone and left no notes.
- We're paying for a CRM edition we use a tenth of.
- Nothing on the market fits the way we sell.
What buyers usually need
The requests that come up most often for this kind of work, and what each one takes to work properly.
01
HubSpot development
Custom properties, objects, workflows, CRM cards and integrations through HubSpot's APIs.
02
Salesforce development
Custom objects, flows, Apex where it's needed, and integrations through Salesforce's APIs.
03
A custom CRM
A CRM built around your pipeline, as a web app you own.
04
Integrations
Your CRM connected to forms, email, accounting, e-commerce and support tools.
05
Data clean-up
Duplicates merged, fields consolidated and records matched to their real owners.
06
Reports people use
Pipeline and activity reports built from the fields your team actually fills in.
Tools that come up most: HubSpot (workflows, custom objects, CRM cards, APIs), Salesforce (Flow, Apex, Lightning, APIs), Pipedrive, Zoho CRM, GoHighLevel, Python, Node.js, PostgreSQL, QuickBooks, Xero, Shopify, Stripe, Gmail, Outlook.
What you get
Concrete pieces, each one something you can open and check when it's done.
CRM customisation
Objects, fields, pipelines and automation set up to match how you sell.
HubSpot or SalesforceIntegrations
Two-way syncs with error alerts and a run log.
APIs, webhooks, n8nCustom CRM
A web app with your pipeline, contacts, tasks and reports.
React, Python or Node.js, PostgreSQLData clean-up
A cleaned database and a written list of what changed.
Imports, dedupe rulesDocumentation
How each automation works and who to ask, written for your team.
Run bookTypical projects
Example packages to show the shape of the work. These are examples, not past clients; yours gets its own written scope.
Example package
CRM integration
Your CRM connected to the tools around it.
You get
- Systems and fields mapped
- Sync with error alerts
- Test log
- Documentation
Example package
Custom CRM
A CRM built for the way you sell, hosted in your account.
You get
- Written scope
- Pipeline, contacts and tasks
- Reports
- Code and docs
How we approach it
The habits that keep this kind of project from going wrong.
1
The right CRM first
If HubSpot or Salesforce fits with settings alone, we will say so before writing code.
2
Your accounts
We build in your CRM and cloud accounts with access you can remove.
3
Tested with real records
Every automation runs on real examples before it's switched on.
How we work
A written scope first, then working progress you can check, then a proper handover.
You describe it
Tell us what you need in your own words, and which tools you already use. A few lines is plenty to start.
A written scope
We reply with a short written scope: what gets built, what is out of scope, which accounts we need, and how we'll both know it works. You know what you're getting before work begins.
Milestones you review
The work is split into milestones. At each one you see it working in your own account and sign it off before we go on.
Handover and a 30-day fix window
You get the working system, its documentation and a walkthrough. If anything we built breaks in the next 30 days, we fix it at no charge.
What shapes the scope
- Which CRM and edition
- Number of systems to connect
- Amount of data to move or clean
- Custom objects or a custom CRM
Always included
- A written scope before work starts
- Milestones you review and sign off
- Documentation and a walkthrough at handover
- A 30-day window for fixes, at no charge
Pushbuild has built software for businesses since 2010, for more than 40 clients. Every project is led by a former public-company CTO, based in Massachusetts. See example builds.
Questions people ask first
Should we use HubSpot, Salesforce or a custom CRM?
It depends on your process, team size and the systems around it. We compare them against your needs in the scope, and our HubSpot vs Salesforce page covers the basics.
Can you work in our existing CRM?
Yes. Most projects start in a CRM the business already has.
Can you move us from one CRM to another?
Yes. We map the fields, move records and history, and check the totals before you switch.
Do we need a particular edition?
Some features need higher editions. The scope says which features the work uses, so you know before we start.
What happens after handover?
For 30 days we repair anything we built that does not work as the scope describes, at no charge. After that, further work is scoped the same way and agreed with you before we start.
Do it once, we automate it. Show us the job one time and it runs on its own after that, in the tools you already use. Not sure where to start? Start with an Automation Audit.
Tell us what you need built.
Email a few lines about what you want and which tools you use, or call. We reply with questions or a written scope.
hello@pushbuild.com