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.

Explore Our Story →

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

OUR STORY

Responsibility must be explicit.

Explore Our Story →

The People Behind Sant

Jeevan Daniel Rajamani, founder of Sant

Jeevan Daniel Rajamani

Founder
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

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.

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

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.

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.

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.

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.

Work With
Someone Accountable.

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