CRM selection and fit assessment
We map how your organisation actually sells and serves, then compare that against what HubSpot, Salesforce and similar products do well. The output is a short recommendation with the trade offs written down.
Solutions · CRM Systems & Integration
A CRM only earns its keep when the data is clean, the pipeline matches how you really sell, and the people who use it daily are not fighting it. We select, configure, build and connect CRM systems that fit your process.
You own the code and IP Weekly demos Reply within one business day
Agent running - queue empty
Flow 04
01
Trigger
Webhook
02
Enrich
Normalise
03
Decide
Policy
04
Act
Resolve
Run log
> Matched 42 records
> Routed 7 exceptions to a human
> Closed 35 tickets automatically
35
Auto-resolved today
6h
Engineer time saved daily
OlDevs is a full-stack technology studio in Vancouver, British Columbia that selects, configures and builds customer relationship management systems.We help organisations choose between an off the shelf CRM such as HubSpot or Salesforce and a custom build, then handle the data model, pipeline design, automation and integration with the website, marketing platforms, accounting and ERP. Most teams are better served by configuring a product properly than by building one from scratch, and we say so when that is the case. Request a quote to scope your CRM project.
Key facts
The short answer
We map how your organisation actually sells and serves, then compare that against what HubSpot, Salesforce and similar products do well. The output is a short recommendation with the trade offs written down.
Discovery · Build or buy · Platform review
Fields, objects, ownership rules and deduplication. A CRM decays when nobody agrees what a lead, an account or a closed deal means, so we settle the definitions first and enforce them in the schema.
Data model · Deduplication · Validation
Stages that reflect real decisions, not wishful ones. We design pipelines with clear entry and exit criteria, required fields per stage, and forecasting views managers can trust without a spreadsheet on the side.
Pipelines · Forecasting · Reporting
Assignment rules, reminders, task creation, quote and renewal sequences, and handoffs between sales, delivery and support. We automate the steps people forget, and leave the judgement calls to people.
Workflow · Automation · Handoffs
Two way connections to your website forms, marketing platforms, accounting and ERP, support desk and calendars, built with retries, logging and a plan for what happens when an upstream system is down.
APIs · ERP · Marketing platforms
Moving off spreadsheets or an older CRM without losing history, plus the training, documentation and first weeks of support that decide whether the system gets used or quietly abandoned.
Migration · Training · Support
Process
Discovery
We interview the people who will use the system daily, walk the current process end to end, and profile the data you already hold in spreadsheets or an existing CRM.
Selection and design
A written recommendation on buy versus build, followed by the data model, pipeline stages, permissions and the integration map. You approve this before anything is configured.
Build and configure
Configuration, custom objects and any code we do need, delivered in weekly increments with a working demo you can click through and comment on.
Migrate and test
Trial migrations you review before the real one, integration testing against live systems, and a rehearsal of the cutover so launch day holds no surprises.
Launch and support
Go live with training in small groups, quick reference documentation, and a support window while habits form and the first awkward edge cases surface.
How we work
We document how leads arrive, who touches them and where deals stall before comparing any platform. Choosing the software first is how organisations end up bending their business to fit a demo.
Objects, fields, ownership and definitions are settled and documented before configuration starts, so a report means the same thing to sales, finance and leadership.
Anything the product does well out of the box stays out of the box. Custom code is reserved for the parts that carry real advantage or that no product on the market handles.
Every connection gets logging, retries and an alert when it stops. Silent integration failures are the usual reason a CRM slowly stops matching reality.
Validation, deduplication and enrichment run at the point of entry, not as an annual cleanup project. Hygiene is a design decision far more than it is a maintenance task.
Training, documentation and a named person to ask are scoped into the project, not added afterwards. A system nobody uses is a failed project however well it is built.
Who it's for
Multiple teams, existing ERP and finance systems, and a real cost to bad data. We handle permissions, regional or divisional pipelines, and the integrations that keep the CRM in step with systems of record.
Membership, casework and stakeholder relationships rarely fit a sales pipeline cleanly. We adapt the data model to members, files and renewals, with accessible interfaces and bilingual English and French capability where needed.
Head office needs a consolidated view; each location needs a simple daily tool. We design shared standards and reporting while keeping location level records and permissions properly separated.
Usually the move off spreadsheets. We set up a CRM that fits how you sell today without over engineering it, so it can grow with the team rather than being replaced in a year.
Weekly
Working demo cadence
One business day
Reply to every enquiry
Full
Client ownership of code and data
FAQ
Buy first in most cases. A properly configured HubSpot or Salesforce usually covers standard sales and service processes better than something built from scratch, and a widely used product brings an established ecosystem, a documented support path and people who already know it. Building makes sense when your process is genuinely unusual, when the product forces a data model that breaks your business, or when the CRM has to live inside an application you already own.
It depends on how many objects, integrations and users are involved, and on how clean your current data is. We scope it after discovery and give you a written plan rather than a guess. You will see a working demo every week from the first sprint, so progress is visible long before launch. Request a quote and we will scope it properly.
Yes, and it is one of the most common starting points. We profile the spreadsheets first: duplicates, inconsistent naming, half filled columns, dates in three formats. Then we agree the rules for cleaning and merging, run a trial migration you can review, and only cut over once you are satisfied with the result.
Website and landing page forms, marketing and email platforms, accounting and ERP systems, support desks, calendars and phone systems. Many of these have supported connectors that we configure rather than code. Where no connector exists, or where the supported one does not carry the fields you need, we build the integration and monitor it.
By removing the reasons not to. That means fewer required fields, sensible defaults, automation that fills in what the system already knows, mobile access for people who work away from a desk, and reports managers genuinely use so the data has visible consequences. We train in small groups and stay available through the first weeks.
You do. Clients own all code, designs, accounts and IP produced by OlDevs, and CRM accounts are created in your organisation's name from the start rather than ours. Licences with the CRM vendor are held by you directly. If you move to another agency later, nothing has to be untangled or handed back.
Yes. The studio is in Vancouver, British Columbia and we serve clients elsewhere remotely, with video calls scheduled in your time zone and on site visits when the work calls for it. We can also work bilingually in English and French where your users, records or reporting require it.
Let’s connect
Tell us what you’re building. We’ll reply within one business day with next steps and a tailored quote — no obligation.
Thanks — we’ll reply within one business day.