Fit call
We check whether the problem and the way we work fit together. For the first 20 minutes we sell nothing — we ask about the process, what the problem costs, and who owns it on your side.
Salesforce built so your team wants to use it.
CRM implementations and migrations for growing B2B companies. We start with your process and your data, not a feature catalogue — and always with a paid diagnosis you keep, even if someone else does the build.
AccountNordis GroupFollowNew ContactNew CaseNew Note
- Type
- Customer - Direct
- Phone
- +48 22 555 01 20
- Website
- www.nordis.example
- Account Owner
- Kacper Walat
- Account Site
- Industry
- Manufacturing
RelatedDetails
We found no potential duplicates of this Account.
Contacts (1)New
Marta Zielinska
- Title:
- Sales Director
- Email:
- m.zielinska@nordis.example
- Phone:
- +48 22 555 01 24
View All
Opportunities (3)New
Nordis — ERP rollout
- Stage:
- Negotiation
- Amount:
- PLN 4,200,000.00
- Close Date:
- 30/09/2026
Nordis — Service
- Stage:
- Proposal
- Amount:
- PLN 1,800,000.00
- Close Date:
- 14/11/2026
Nordis — Licence expansion
- Stage:
- Closed Won
- Amount:
- PLN 620,000.00
- Close Date:
- 02/07/2026
View All
ActivityChatter
Filters: All time • All activities • All types
Refresh ·Expand All ·View All
Upcoming & Overdue
No activities to show.
Get started by sending an email, scheduling a task, and more.
To change what's shown, try changing your filters.
Show All Activities
Six sentences we hear most
If two of these sound familiar, a conversation is worth it. If none do, you probably don't need us yet.
Services
We start with a step that stands on its own
We don't ask you to commit to a six-figure project at the first meeting. We ask you to commit to a diagnosis, after which you'll know whether anything is worth building at all.
What we won't take as a first project
Full CPQ and Revenue Cloud, ERP as the centre of the project, portals, complex omnichannel, multi-country rollout on fixed price, and anything with no time for UAT, training and hypercare. We'd rather say this now than in week eight.
Five stages. Each ends in a decision.
You can walk away after any stage — holding a finished deliverable, not half a system.
01 · 20 minutes 02 · 7–10 days Blueprint
A paid diagnosis of process, data, org and risk. It ends in a decision presentation: what to do, in what order, at what cost, and what to deliberately not do. The report stays with you whoever you pick to build it.
03 · 2–10 weeks Launch or Rescue
A scoped project with a closed backlog and acceptance criteria. We show working increments at least weekly — there is no “we'll come back in two months with something finished”.
04 · 2–4 weeks Adoption and hypercare
Role-based training, playbooks, office hours and an adoption dashboard. We measure whether the process actually changed how people work, not whether users clicked through screens.
05 · optional Managed or Phase 2
Further work only where it earns its cost. If we don't see a backlog worth funding after hypercare, we'll say so.
Evidence
We're new. Here's what we're missing
Every agency in this market calls itself a trusted partner. We're a new firm, so instead of asking for that, we put both columns on the table — and only then say what we commit to.
What we haveVerifiable
- 3+ years of experience on both sides of the tableKacper — Salesforce developer · Kuba — sales, discovery and adoption
- Three Salesforce certifications, a fourth in progressPlatform Developer I · JavaScript Developer I · Platform App Builder — Verify on Trailhead
- Two people on every call, both accountable for the outcomeNo salesperson who disappears after the signature
- An entry product that stays with youThe Blueprint: process map, scorecard, risks, roadmap
What we don't have yetAs of today
- Official Salesforce partner statusWe're preparing for the Consulting Partner programme
- Case studies under this brandWe did those implementations at previous employers, not as Muphird
- Client logos on the siteNot until we have consent — someone else's logo without permission is not a reference
- Hundreds of implementations and a hundred-person teamWhich is why we cap the first scope on purpose: one department, 15–50 users
Nothing in the right-hand column goes away because we left it out. So instead of asking you to trust us, we give you six things in writing.
Commitments
Each one costs us something if we break it.
These aren't slogans — they're clauses that go into the contract or get said on the fit call, before you sign anything. The rail above each card says where that commitment binds.
What's in the Blueprint- DocumentIn the contract
The Blueprint stays with you
Even if you hand the implementation to someone else. The process map, scorecard, risks and roadmap are yours from the moment you accept them.
- ScopeBefore kickoff
Acceptance criteria in writing
We agree them before we start, not after. If something isn't in the criteria, it cannot become an argument at the end.
- QualificationOn the fit call
We'll say no at the start
We don't take projects that exceed the safe capacity of two people — and we say so in the twentieth minute, not in the eighth week.
- HandoverIn the contract
No lock-in
We don't build things that are deliberately hard to take over. Every implementation ends with documentation and a handover — to us, to you, or to anyone else.
- AuditIn the contract
No finding is a finding too
If the audit turns up nothing significant, you get that in writing. Sometimes the problem isn't in Salesforce — then we say so plainly.
- PriceAfter the Blueprint
A fixed price, not an estimate
We quote the implementation only once the scope is counted — and from then it doesn't move. The Blueprint cost is credited against the first stage.
Reach
Three markets we have already worked in
Not as Muphird — at previous employers. But the language, the time zone and the way a rollout gets received in a given market are things you cannot make up by reading. These three we know first-hand.
- PolandWarsawHome market. Implementations and org development in Polish, with Polish sales and service processes.
- SwitzerlandZurichRun in English, under the documentation and compliance discipline the DACH market expects.
- United StatesNew YorkWork across a time-zone gap — rollout and support planned around somebody else's working calendar.
The pins mark the markets of clients we worked for before founding Muphird. No names, no logos until we have consent — the same rule as the column above.
Two people. Both of them talk to you.
At a larger firm you talk to a salesperson, and the project is built by someone you meet at kickoff. Here both of those people are on the first call, and both own the outcome.
Architecture and delivery
Kacper
Owns the technical solution, quality, risk, and making sure the org can still be changed afterwards without a prayer. Writes the code he then maintains.
- 3+ years as a Salesforce developer
- Platform Developer I
- JavaScript Developer I
- Platform App Builder
- Agentforce Specialist — in progress
Sales, discovery and adoption
Co-founder
Owns the conversation about process and value, runs discovery with process owners, and delivers the training. Training is part of the product here, not a free extra.
- Business discovery
- Workshops with process owners
- Role-based training
- Adoption measurement
The questions you'll ask anyway
Are you an official Salesforce partner?
Not yet — we're preparing our application to the Consulting Partner programme. We operate as an independent implementation team. In practice this means we don't have access to some partner-only Salesforce resources; it doesn't change the scope or the quality of the work we do.
What does it cost?
We give ranges on a call, not on a page — a price set without knowing your processes, data and integrations is guesswork, and guesswork hurts in both directions. A 20-minute fit call gets you the range for a Blueprint. We quote a fixed price for the build only after the Blueprint, once the scope is actually counted. What moves that number up or down is listed against each service above.
Why pay for a diagnosis when others do it free?
Because a free diagnosis is a cost of sale, so it has to end with a proposal — that's arithmetic, not an accusation. A paid one is a product, so it ends with documents: the process map, the scorecard, the risks and the roadmap, and they stay with you even if someone else runs the build. If you pick us, the Blueprint comes off the first phase of the implementation.
How much of our time will this take?
Blueprint: 3–5 hours per involved person, spread over 7–10 days — workshops with process owners plus access to the org and the data. Implementation: about half a day a week for the sponsor and the decision maker, plus UAT and training in the week before go-live. We say this on the fit call, because a project with no time on your side does not end well — and we don't take those.
There are two of you. What if the project outgrows you?
That's exactly why we cap the first scope: one department or country, 15–50 users, one source system, 1–2 integrations. We don't take projects that don't fit the safe capacity of two people — and we say so on the fit call, not in week eight.
Who maintains it after you're done?
Every implementation ends with knowledge transfer and documentation. You can take the system over entirely, keep us on Managed Salesforce with defined capacity, or hand it to any other vendor. We don't build things that are deliberately hard to take over.
What if the audit finds nothing significant?
That's a result too, and you'll get it in writing. Sometimes the problem isn't in Salesforce at all — it's in the process, or in nobody owning the data. We'll say that plainly rather than sell you an implementation that fixes nothing.
Start with twenty minutes
On the fit call we check whether the problem and the way we work fit together. If they do, within one working day you get a Blueprint proposal with scope, timeline and a fixed price. If they don't, we'll tell you straight away.
No sales deck. The first 20 minutes are questions about your process.