10 · AI, processes, CRM and sales
CRM and integrations
One customer record everyone trusts, connected to the systems where the work happens.
In short
A CRM is only as good as the data in it and the systems around it. When sales, invoicing and the shop each hold a different version of a customer, people stop trusting all three.
I build against APIs every week, from weather models to search data and email. A Salesforce or HubSpot project gets the same order of work: model the data, then connect, then migrate. Neither has a case study in my portfolio yet.
What's included
Salesforce implementation
Objects, fields, pipelines, permissions and automation set up for how your team sells, not for the default demo.
HubSpot implementation
Properties, pipelines, forms, email and workflows configured, with your website connected.
API integrations
Your CRM connected to ERP, invoicing, e-commerce and email tools, through their APIs or a sync platform.
Data migration
From spreadsheets or an old CRM, with fields mapped, records matched and a test run before the switch.
Data cleanup
Duplicates merged, fields standardised and rules added so the mess doesn't come back.
How I run it
Audit
The systems, the data in them and who relies on what.
Data model
One definition of a customer, a deal and an order, agreed with the people who use them.
Configure
The CRM set up, with permissions and only the fields that matter.
Integrate
Connections built and tested, with errors logged and an alert on failure.
Migrate and train
A test migration, the real one, and short training for the team.
Content Monitor · Site Scanner · Polaris CMS
Run on my own tooling
My dashboard is itself an integration project: it pulls from several APIs and keeps them in step. That experience is what I bring.
Content Monitor
The dashboard every live site is run from
Many APIs, one view
Search Console, Google Analytics 4, DataForSEO, the CMS of every site and the social scheduler, pulled into one dashboard on schedules.
Access per client
Clients get a login limited to their own sites and a personal API token for their own agent: the permission model a CRM integration needs.
Inboxes and outreach
Support inboxes and outreach emails with reply and bounce detection, kept next to the sites they belong to.
Polaris CMS
My own CMS, this site included
An API for other systems
The CMS has an API with keys, so other systems and AI agents can read and publish content.
Infrastructure
Docker on my own servers, behind Cloudflare
Sync jobs I host
Integration and sync jobs can run on my servers in Docker, next to the sites, with backups.
Proof
- Project Grzybolog Weather data for 380 points pulled from the Open-Meteo API twice a day and stored in Postgres.
- Project PlantAlong Frost alerts by email with double opt-in and a personalised PDF calendar.
- Project PolishPal Supabase for the data and ElevenLabs for the Polish recordings, connected in one Next.js app.
Where this stands The links above show API integration work. Salesforce and HubSpot implementations have no case study here yet.
Questions
Salesforce or HubSpot?
HubSpot is usually quicker to start and easier for small teams, especially with marketing in the same place. Salesforce suits complex sales processes and larger teams that need deep customisation. I compare them on your process, not on feature lists.
Have you implemented Salesforce or HubSpot before?
Not as a Scentro project you can see here. I build API integrations all the time, and this page describes exactly how I would run a CRM project. Ask me about the details.
Can you clean up the data we already have?
Yes. I export it, find the duplicates and gaps, agree the rules with you and import the cleaned version with a log of every change.
Related services
All services →Tell me what you need
A few lines are enough: what you want to build, fix or automate, and any date that matters. I reply in English or Polish.