Four ways to work with Kanixa

Pick the model that fits your team today. You can change it as your needs change.

Fixed-scope project

Best for

Defined outcomes like an integration, an AppExchange release or a migration.

How it works

Agreed scope, milestones and price after a discovery call. Change requests are estimated before work starts.

Best for

Product roadmaps and long programmes where priorities change.

How it works

A stable team of developers, a consultant and an architect working only on your backlog, billed monthly.

Best for

Orgs that need steady admin, development and release support.

How it works

A monthly block of hours across admin, development and architecture with agreed response times.

Best for

In-house teams that need certified Salesforce skills quickly.

How it works

Kanixa specialists join your team, process and tools, from a few weeks to many months.

1
Share your brief
Tell us the goal, the systems involved and the deadline. A short call is enough to start.
2
Scope and plan
We return a written scope, architecture notes, a timeline and the team who will do the work.
3
Build in short sprints
Demos every one or two weeks in a sandbox you can click through.
4
Test and deploy
User acceptance testing, a rehearsed deployment and a rollback plan.
5
Train and support
Handover documents, training and an agreed support period, or an ongoing retainer.

Do you publish prices?

No, because scope varies too much for a list price to be honest. After a short call we send a written estimate within a few working days.

Which time zones do you cover?

We plan overlap hours with clients in North America, the UK, Europe and Australia, and agree meeting times at kickoff.

Can we switch models later?

Yes. Many clients start with a fixed-scope project and move to a retainer or dedicated team once the first phase is live.

A 30-minute call with a Salesforce architect. You'll leave with a clear next step, whether or not we work together.