About

OUR STORY

Sant was built on one idea: when organisations hand over their systems, decisions, and growth, someone should be named for the outcome.

Scope is defined. Responsibility is named. We stay involved past delivery.

OUR STORY

Responsibility must be explicit.

Explore Our Story →
OUR STORYOUR STORYOUR STORYOUR STORYOUR STORYOUR STORYOUR STORYOUR STORYOUR STORYOUR STORYOUR STORYOUR STORY
The Background

Twenty Years of Practice.

Sant draws on more than two decades of work across technology, consulting, and delivery. The projects were in settings where systems carried real consequences, where decisions had downstream impact, and where mistakes were costly.

Across those years, the same few things broke most engagements. Fixing those is the work.

Technology is rarely the real problem. Decision-making without context is.

Senior delivery. Small team. Direct involvement.

IN BRIEFIN BRIEFIN BRIEFIN BRIEFIN BRIEFIN BRIEFIN BRIEFIN BRIEFIN BRIEFIN BRIEFIN BRIEFIN BRIEF
In Brief

Sant Means True.

The name comes from the Scandinavian word for "true," carried through Danish, Norwegian, and Swedish.

It was picked because it sets the bar. The work either holds up to the meaning, or it does not.

One Nonprofit. Every Quarter.

Sant gives one New Zealand nonprofit a real piece of work every three months. A site, a tool, or a system. The schedule is the promise. The recipients are named publicly.

See the programme
ORIGINORIGINORIGINORIGINORIGINORIGINORIGINORIGINORIGINORIGINORIGINORIGIN
The Location

Built in New Zealand.

Sant is based in New Zealand. The country offered stability and the space to build something careful.

Building a family and a home here reinforced a preference for work that still holds up in five years. Trust is earned through consistency, not claimed in a pitch.

Built in New Zealand. Accountable locally. Working with clients globally.

LEADERSHIPLEADERSHIPLEADERSHIPLEADERSHIPLEADERSHIPLEADERSHIPLEADERSHIPLEADERSHIPLEADERSHIPLEADERSHIPLEADERSHIPLEADERSHIP
The Leaders

The People Behind Sant

Jeevan Daniel Rajamani

Background

Jeevan founded Sant after twenty years of technology, consulting, and delivery work spanning enterprise systems, regulated environments, digital platforms, and advisory engagements. Those decisions carried real operational and financial weight. At Sant, clients work with him directly.

Read the twenty-year story

Rae Camille Rajamani

Background

Rae is a senior SAP consultant. She works on large-scale enterprise systems, and her background informs how Sant thinks about architecture and risk.

Context

Why This Matters

Mentorship and Influence

Years working under strong leaders in UK enterprise environments, and alongside experienced business owners in New Zealand, shape how Sant operates today.

Built Lean, Designed to Grow

Sant is small on purpose. Leadership stays hands-on. As the company grows, the plan is to develop capability in New Zealand and mentor the next generation of practitioners.

Growth stays deliberate.

PHASESPHASESPHASESPHASESPHASESPHASESPHASESPHASESPHASESPHASESPHASESPHASES
Methodology

Launch. Grow. Scale.

Three phases. Each with a clear purpose, defined principles, and a specific outcome.

Phase 1

Launch

Turn intent into a usable, working asset.

Focus

Clarity of scope and disciplined execution.

Principles
  • Scope settled before work begins
  • Defined outcomes, not vague promises
  • Usable software over abstract documentation

Working systems create better conversations than speculative plans. Documentation supports maintenance and handover. It does not replace delivery.

Phase 2

Grow

Turn activity into insight, and insight into progress.

Focus

Performance, learning, and steady improvement over time.

Principles
  • Measurement before optimisation
  • Focus over channel overload
  • Learning that compounds

Grow reveals patterns. It shows what is working, what is not, and where effort should be concentrated.

Phase 3

Scale

Prepare systems and organisations for increased volume, variation, and responsibility.

Focus

When early solutions start to strain. Platforms feel limiting. Decisions slow down.

Principles
  • Architecture before expansion
  • Stability before speed
  • Durable choices over quick fixes

Scale creates resilience. It ensures growth does not introduce fragility.

VALUESVALUESVALUESVALUESVALUESVALUESVALUESVALUESVALUESVALUESVALUESVALUES
Values

What We Optimise For.

Speed alone is not the goal. We optimise for work that holds up. That means:

01Maintainability of systems
02Predictable behaviour under load
03Reduced cost of rework
04Clean handover at every stage
Litmus Test

Every engagement sits under one question: 'Will this still make sense in twelve months?'

STANDARDSSTANDARDSSTANDARDSSTANDARDSSTANDARDSSTANDARDSSTANDARDSSTANDARDSSTANDARDSSTANDARDSSTANDARDSSTANDARDS
03 · Enterprise Rigour

Standards Drawn from Regulated Environments.

Our approach comes from enterprise-grade systems and regulated delivery environments, including SAP ecosystems. Not from web design trends.

That discipline applies to every project, regardless of size:

01

Documentation is rigorous, not an afterthought.

Every decision, dependency, and deliverable is recorded with the same care that enterprise systems demand.

02

Risk is assessed before code is written.

Risks, dependencies, and edge cases are identified upfront so there are no surprises at delivery.

03

Security is a baseline, not an upgrade.

Security is embedded from day one.

05 · Badges vs Standards

Vendor badges can expire. Standards endure.

Credibility shows through:

The environments we have worked in.
The decisions we are trusted to make.
The responsibility we carry for outcomes.

Credibility sits in the work,

not on the wall.

TECHNOLOGYTECHNOLOGYTECHNOLOGYTECHNOLOGYTECHNOLOGYTECHNOLOGYTECHNOLOGYTECHNOLOGYTECHNOLOGYTECHNOLOGYTECHNOLOGYTECHNOLOGY
Philosophy

Business First, Tools Second.

Every technology decision begins with a business question:

01
What problem are we solving?
02
Who will maintain this in three years?
03
What happens when requirements change?
04
What is the cost of getting this wrong?

Only then do we select tools. That prevents over-engineering, lock-in, and expensive rewrites.

STACKSTACKSTACKSTACKSTACKSTACKSTACKSTACKSTACKSTACKSTACKSTACK
The Stack

The Stack

Sant works across a selected set of platforms balanced for reliability, flexibility, and maturity. We understand them, and we choose them deliberately.

The Stack

ContentandCommerceEcosystems

WhyChosen for their ecosystem maturity, interoperability, and the availability of talent to maintain them.
Use CaseWhen clarity, editorial control, and speed-to-market matter.
The Stack

ApplicationandSystemDevelopment

WhyWhen specific business logic cannot be constrained by off-the-shelf software.
Use CaseMembership systems, Internal tools, Complex data handling.
The Stack

CloudandInfrastructure

WhyInfrastructure that grows without surprises.
Use CaseStability, security, and operational clarity over novelty.
The Stack

IntelligenceandAutomation

WhyApplied where it creates measurable value: reducing effort, improving accuracy, or making work possible that wasn't before.
Use CaseContent generation, code acceleration, creative production, workflow automation, and intelligent data processing.
AI & AUTOMATIONAI & AUTOMATIONAI & AUTOMATIONAI & AUTOMATIONAI & AUTOMATIONAI & AUTOMATIONAI & AUTOMATIONAI & AUTOMATIONAI & AUTOMATIONAI & AUTOMATIONAI & AUTOMATIONAI & AUTOMATION
AI and Automation

Applied Carefully, Not Blindly.

When sensitive organisations adopt AI, they need certainty: data stays private, decisions stay accountable, and control stays human.

Data PrivacyHuman OversightGovernanceAccountability

Data Privacy

No client data used for model training. Processing within approved boundaries. Full data residency and deletion guarantees.

Human Oversight

Every AI output passes through human review. Automated decisions include override controls and audit trails.

Governance

Role-based access, encryption at rest and in transit. Every deployment meets institutional compliance requirements.

Accountability

Clear documentation of what the AI does, how it decides, and who is responsible. No black boxes.

Let's Talk

Work With
Someone Accountable.

If this is how you want your work done, get in touch.