3–4x faster
Speed: weeks, not months
Production MVP typically in a couple of weeks, full project typically in 5–8 weeks. Sprints are one day long, so feedback is immediate and value flows from the very start — not just at the end of the project. Licenses start delivering returns before a traditional project would even be out of the design phase.
No surprises
Predictability: fixed price per phase
The total budget is known before kick-off. No hourly billing, no Change Request add-ons. AI usage costs are included in the price.
100% success rate
Quality: mandatory production testing at every wave
Every phase is verified in production before closure. Code, documentation, and architecture decisions move at the same pace. No technical debt.
Using Salesforce but not getting enough out of it?
Do any of these challenges sound familiar?
- Projects drag on for months and ROI keeps getting pushed further away
- A change deployed to production turns out to be broken only once it’s in use
- Purchased licenses sit underutilised and the investment stalls
- Knowledge lives in one person’s head — no documentation, no continuity
We encounter these challenges regularly, and we wanted to bring a completely new and unique solution to the table. Want to hear more? Book a time in the calendar and we’ll find a suitable starting point — and show you the results in practice.
How does the Loikka Way work?
The Loikka Way is Finland’s first AI-assisted Salesforce delivery model. We haven’t just “given a consultant an AI tool” — we’ve built a new way of running projects on top of 20 years of Salesforce expertise. The Loikka Way is built on six cornerstones that together ensure speed, quality, and predictability.
The six cornerstones of the Loikka Way:
- Clear roles — humans lead A Loikka team member acts as architect and Product Owner. AI is the developer and handles repetitive work. Humans own every decision. AI does not reach production without approval.
- 1–2 day sprints — every phase is a release No two-week sprints. A daily cycle: plan → build → DoD check → deploy to production. Phase = done, tested, live.
- Definition of Done — a six-point requirement Every phase is verified against a six-point DoD checklist before closure. Mandatory live verification in production — no “it works on my machine” deliveries.
- Documentation discipline — no knowledge locked in one head Code, architecture decisions, and user guides are updated in step with the code. Five authoritative documents — one per question.
- ADR framework — decisions are recorded Every architecture decision is logged in an Architecture Decision Record. No tribal knowledge — a new developer can get up to speed in a day.
- Idea pipeline — backlog under control Design → Approved → In Progress → Done. Clear prioritisation, no mid-sprint “could we also add…” scope creep.
How do we get started?
We design a suitable pilot together — one where we can demonstrate the Loikka Way in action. No commitment required.
1. A short sparring session: 30 minutes, free of charge
We look at how the Loikka Way fits and how much value it can deliver. We’ll tell you straight if we don’t think it’s the right fit. No sales pitch.
2. Pilot: one well-scoped deliverable
We deliver one suitable piece of work that demonstrates the advantages of the Loikka Way in practice. Fixed price, clear scope, all the way to production.
3. Ongoing collaboration on the Loikka Way
From the pilot onwards, we continue as the situation warrants: individual projects or an ongoing partnership. Always at a fixed price and with a written agreement.
Loikka Solutions x Firemind: AI-Powered Salesforce Audit (Delivered the Loikka Way)
Firemind needed an independent review of their Salesforce Enterprise environment covering sales, delivery, finance, and AWS partner integrations. Loikka delivered a comprehensive environment audit in two weeks — a project that traditionally takes a month or more. The AI-native approach covered licensing optimization, security hardening, custom objects, automations, and integration health — at a fraction of the typical cost.
“Thorough results, comprehesive documentation and fast delivery with a fair price.”
Petri Sane
Director, IT and Compliance, Firemind
Want to see the Loikka Way in action?
Book a free 30-minute sparring session. We’ll walk through your situation together and tell you straight how the Loikka Way fits your Salesforce development.
Usein kysytyt kysymykset
What does “disciplined delivery” mean?
It means that agreed practices are not compromised, even under time pressure.
In the Loikka Way, disciplined means three concrete things:
Scope is locked before development begins. Every phase’s scope is documented and approved with the Product Owner before a single line of code is written. Changes go to the next phase — not mid-sprint.
Definition of Done is mandatory. No exceptions. Six checkpoints are reviewed before every production deployment. “Works on my machine” is not acceptable — live verification in the production environment is required.
Decisions are recorded, not remembered. Every architecture decision is documented in an ADR (Architecture Decision Record). Documentation is updated in step with the code — not retrospectively.
In practice, this means customers get predictable deliveries, and every release is genuinely complete.
Does AI have free rein in our production environment?
No. AI does not reach production without human approval. A Loikka architect reviews every change before it goes to production. The customer’s Product Owner approves every phase at the scope and release stage. A human always owns every decision.
Does the Loikka Way work with our existing Salesforce environment?
Yes. The Loikka Way works on top of any existing Salesforce environment and does not require a new org or structural changes. Only the release cadence speeds up.
What does AI do with our Salesforce data?
AI does not process customer’s business data. In the development process, AI writes code, tests, and documentation — it does not read or analyse CRM data. The AI interfaces used comply with data protection regulations, and data processing is always agreed in writing at the start of the project. EU Data Boundary is available when required.
Can our internal Salesforce admin be involved?
Yes, and it’s often the best option. An internal admin works excellently as Product Owner. They know the environment, the users, and the business needs better than any external party. When the project ends, your organisation is left with a completed implementation, documented architecture, and a clear understanding of the decisions made. No vendor dependency.
Who is responsible if something breaks in production?
Loikka carries implementation responsibility. Bug fixes are included in the phase price — no separate invoices for fixes. Because every phase is tested in production before closure, disruptions are rare.
How much time is expected from the Product Owner?
Around 60–90 minutes per day during a sprint. The key moments are: Monday planning (1 h) and Friday release review (30–60 min).
How is a fixed price possible?
The fixed price is based on a clear scoping process. Before each phase, the scope is locked together with the Product Owner. Loikka carries the risk of how long the technical implementation takes.
Is the Loikka Way only for large projects?
No. The Loikka Way scales from small individual features to large development projects. A pilot can be a single integration, a Flow automation, or an Agentforce rollout.
We have an existing Landscape review and legacy documentation. How are those taken into account?
They are a valuable starting point and we read them before the kick-off.
Existing materials (Landscape review, architecture descriptions, requirements documents, old project reports) are analysed before the first joint session. This means we arrive at kick-off with a pre-informed view — not starting from a blank slate.
In practice, this means:
Landscape analysis: We map what has already been done, what is worth building on, and what should be replaced. AI significantly accelerates this analysis.
Documentation as the basis for scope: Open requirements, identified issues, and prior decisions are surfaced from legacy documents. These form the first version of the backlog.
Identifying conflicts: If legacy documentation is inconsistent with the current state, it is reviewed together at kick-off — we do not assume everything is up to date.
The more material available upfront, the faster we can get moving.
Our scope definition is still unclear. Can the Loikka Way help clarify it?
Yes — this is exactly what the Loikka Way is designed for. Scope does not need to be fully defined before starting. It is clarified in three ways:
A kick-off workshop before the first sprint. We go through objectives, constraints, and priorities together. The output is a written backlog — not just a shared verbal understanding.
Phases break scope into manageable pieces. Rather than having to define the entire project upfront, we agree on a 5–8 week phase scope at a time. Each phase begins with a refinement session where AI analysis is also used — technical feasibility is factored in at the planning stage.
Definition of Done makes scope measurable. Every deliverable has an explicit definition of done — no ambiguity about whether something is finished. This forces concreteness before development begins.
Risk is managed by making every phase fixed-price, with completion criteria agreed in advance.