Architecture
A platform that grows with you
Package structure, data model and coding standards your team can build on for years. Dependencies mapped, decisions written down.
Freelance Salesforce architect and developer
Your Salesforce org keeps getting harder to change.
Every release feels risky, nobody remembers why things were built this way, and the agency that built it has moved on. I'm Alwin van Dijken, and for 14 years I've been making Salesforce safe to change again.
Your team still checks company numbers by hand.
Someone opens the KvK website, copies the answer and hopes it's still right next month. I build Salesforce apps that check companies against the official register, record every check and work wherever the question comes up.
Nobody can explain how your Salesforce org is built.
The people who built it have left, the documentation is out of date, and every change starts with detective work. I map what is there and write down why, so your team can carry on.
A deactivated user is not a cleaned-up user.
Access gets granted by hand, and when someone leaves, only the Active box gets unticked. Profile and permission sets stay: one reactivation for a new assignment and all the old access is back. I automate access in Salesforce, from the first SSO login to the day someone leaves.
In three courses
From problem to proposal
01The problem
Change has become expensive
Code without tests, packages nobody dares to touch, integrations that fail silently.
02How I solve it
One senior builder, start to finish
A review first, then small working steps.
- Architecture with written decisions
- Apex and LWC with tests that prove something
- Ready-made packages where they fit
03How to start
A 30-minute intro call
You describe the situation. Within a week you get a written proposal with scope and price.
01The problem
Checks done by hand
Numbers copied from websites, typos in registration numbers, and no record of what was checked.
02How I solve it
One check, everywhere
Business Registration checks the number offline first, then looks the company up in the official KvK register.
- Sixteen countries' number formats
- Every attempt recorded as evidence
- Sources and limits are configuration, not code
03How to start
A 30-minute demo
In your own words: which registers and which processes. Then a trial in your own sandbox.
01The problem
The knowledge has left
Packages, dependencies and automations nobody fully understands, and decisions nobody wrote down.
02How I solve it
A review with decisions on paper
I go through code, packages and release process, and you get a concrete plan.
- A map of packages, dependencies and data model
- A short decision record for each important choice
- What first, what can wait, what should go
03How to start
A 30-minute intro call
You describe the org. Within a week you get a written proposal for the review.
01The problem
Access that lingers
Access depends on whichever admin granted it, and leavers are only deactivated. It comes up in every audit.
02How I solve it
Access that follows the lifecycle
User Provisioning grants access on the first SSO login and removes it when someone leaves.
- Access from a role mapping you maintain
- Leavers recorded, revoked and dropped to a minimal profile
- A scheduled check for inactive users with too much access
03How to start
Read first, then a demo
The article explains why deactivating isn't enough. Then I'll show you in 30 minutes how it works in your own sandbox.
About me
Hi, I'm Alwin
I'm a freelance Salesforce architect and developer, and I've worked with the platform for 14 years. My work is in government and industry: the municipalities of Amsterdam, Tilburg and Almere, and now Lely. Before that I spent eight years at BrightFox.
I like to do the work start to finish: shaping the architecture, writing the code and making sure your team can carry on without me. What I keep running into on projects, I build as a package, so the next client doesn't have to start from scratch.
Alwin van DijkenFreelance Salesforce architect and developer · Well (L)
Experience
14 years of Salesforce
Recent engagements. Government and industry, from architecture to the last line of code.
- 2026 – now
Lely
Salesforce Engineer
Event registration, onboarding and integrations for an international maker of agricultural robots.
- 2025 – 2026
Municipality of Almere
Salesforce Technical Architect
Layered fflib architecture, REST, SOAP and Platform Event integrations, Experience Cloud and 2GP packages.
- 2025
Municipality of Tilburg
Senior Salesforce Developer
LWC and Apex in service and domain layers, flows and reporting.
- 2023 – 2025
Municipality of Amsterdam
Senior Salesforce Developer
Citizen contact with Omni-Channel and Knowledge, government data integrations and platform accessibility.
Before that, eight years at BrightFox, for clients including Telfort Business, Medtronic, Exact and teams in the UK.
Mise en place
How I work
In a good kitchen everything is prepared before service starts. I work the same way.
- 01
Understand first
We start with the problem and the people who have it, not with the technology.
- 02
Decisions on paper
Every architecture choice gets a short decision record, so your team knows later why things are the way they are.
- 03
Ship small, ship often
Working software in short steps, with tests and a preview you can check yourself.
- 04
Built to hand over
Code, documentation and standards your team can carry on without me.
Blog
From the kitchen
- A deactivated user is not a cleaned-up userUnticking Active keeps every right someone had. One reactivation later, it's all back.
- I moved my registry into Custom Metadata, then moved it backApplying open/closed by the book made the code worse. When configuration is the wrong tool.
- @isTest doesn't protect you from Type.forNameType.forName still finds an @isTest class and creates a working instance, even outside a test. Why that matters for managed packages, and the fix.
Hire the chef, not the agency
Senior Salesforce architecture and Apex, straight from the person who writes the code.