Partners · Recruiters
Freelance Salesforce Architect: working with recruiters
Many of my projects come through staffing agencies, the best ones through recruiters I have worked with before. This page says what you get from me, what I need from you and where my limits are. That way we both know early whether working together fits.
- Answer within 1 working day
- 1 recruiter per request
- Submission only with approval
This is always the current version of my CV. Please do not submit older versions to clients.
- 8years of Salesforce
- 20+enterprise projects
- 25 · 8certifications · Architect
- DE · ENproject languages
Profile
What to contact me for
So you can quickly judge whether a request fits, both are listed here.
Fits
- Enterprise, solution or lead architect roles
- Programmes with several implementation partners
- Architect on the client side between business and IT
- Manufacturing, service, after-sales and B2B sales
- Partner governance, DevOps and SAP integration
Rather not a fit
- Pure admin roles
- Developer roles without architecture decisions
- Roles where the architecture is already fixed and only needs to be signed off
If I know someone who fits better, I will tell you.
Clouds and tools
The deal
What you get, what I need
Working well with recruiters depends on the same things as with any other partner: clear agreements and reliability, on both sides.
You get from me
- An answer within one working dayYou get it even when the answer is no. That way your client does not have to wait for me.
- An honest assessment up frontI tell you up front which requirements I meet and which I do not. That way you can present me to the client with good arguments.
- Exclusively through youSubmissions only with my written approval, through exactly one recruiter per request. If the same role reaches me through others later, I let them know I am already represented, even if their terms are better.
- Availability you can rely onI give you start date and utilisation as I can actually deliver them. If anything changes, you hear it first.
- Loyalty in the projectExtensions naturally go through you, even if the client approaches me directly.
I need from you
- The end clientThat way I can reliably rule out double submissions. I treat the name confidentially.
- Role, phase, decision scopeI need to know whether it is a greenfield project, an existing org (brownfield) or a critical situation, whatever the phase. I also need to know how many partners deliver and who decides.
- Duration, utilisation, start, on-site shareThese basics usually decide whether it fits. Ideally they are in the first message.
- The budget rangePlease name the budget in your first message. Only then do we treat each other’s time with respect and make sure working together is an option at all.
- Feedback after the submissionEven after a rejection, a short and timely reply is essential.
Keeping it fair for both sides
Almost everything can be settled in conversation. On these points, I ask for your understanding that I make no exceptions.
- Submission only with approval: My profile only goes to a client with my consent.
- The profile stays as it is: Please do not add skills, certifications or years of experience I do not have.
- One CV, one version: My CV exists in one version. I do not translate it into German or transfer it into your template.
- No passing on without asking: Please do not pass my profile on to other agencies without asking me first.
- No contacts from past projects: I do not hand out contact details of decision-makers from my previous projects. For business development, please do your own research.
- Agreed is agreed: A rate we have agreed on still applies after the client has said yes.
- Travel time is not free time: I am happy to work on site at the client. The effort of getting there belongs in the calculation, though.
- Contracts that fit the situation: I only sign contracts that actually describe our collaboration. Clauses that are not relevant to it do not belong in them.
- Fair payment terms: You pay my invoice regardless of when your client pays. The payment term is at most 30 days.
- Reasonable non-solicitation: It only covers clients you introduced me to, for at most 12 months.
Process
How a request works
- 01
Request
You send me the request by email or through the form, with end client, role, duration, utilisation, start and budget.
- 02
Answer
Within one working day I tell you whether it fits and give you my hourly or daily rate and availability.
- 03
Approval
You get my written approval for exactly this request.
- 04
Client interview
I prepare for the project, not just for my CV.
- 05
Contract and start
You remain the contact for everything contractual, including the extension.
Terms
Rate per request
I quote my hourly or daily rate for each request individually. It depends on the role I take on, how long the project runs and how often I am on site.
Contract with the company
Your contract partner is my company, FK Solution Design GmbH. I invoice monthly by actual effort and attach a timesheet to every invoice.
Remote and on site
I am flexible here. What works well is running intensive phases and workshops on site together with the project team and then continuing remotely for a few weeks.
Travel
I work from Cologne. When the project needs it, for example before a go-live, I also travel worldwide, but usually no more than once a quarter. I bill travel time in full as working time. I prefer to bill travel expenses at actual cost. If your client prefers a flat rate, that works too.
Contact
A request that fits?
Send me the basics. You get an answer within one working day, even if it is no.
Book a call (opens Microsoft Bookings in a new tab)Pick a slot in my calendar via Microsoft Bookings. Prefer to write? Use the form and I’ll get back to you.
Rather talk right away? +49 221 98656758