SOFTWARE AND SUPPORT
Build a customer portal, connect your systems or improve software that no longer fits. We design and develop around the people using it, the information it needs and the work it must support.
Work directly with Jeevan, based in Christchurch.
01 / 06
Business applications
When spreadsheets, disconnected records or awkward workarounds are getting in the way, the answer may be a tool built around the job. We design internal applications, customer portals and dashboards that bring the relevant information and actions together.
Work we can include
Screens and processes for tracking work, assigning tasks, reviewing information and managing approvals.
Account-based access to relevant records, documents and status information, with permissions defined around each user.
Organise records and present the information people need to make decisions or complete a task.
Define what different users can view, change and approve across the application.
Agree expected use, data volumes and recovery needs, then design and test against those requirements.
02 / 06
Customer-facing software
Turn a product idea or an existing application into software your customers can use. We plan the user journeys, account structure and essential features, then build around an agreed release rather than trying to include every future possibility at once.
Work we can include
Define the people, journeys and features the next release needs to support, with later additions kept distinct.
Registration, sign-in and access rules, including separate customer or team workspaces where required.
Billing connections, plan access and subscription workflows for the business model being developed.
Features that let customers manage relevant account information, records and requests themselves.
Logging, monitoring and maintenance requirements considered alongside the product features, not left until launch.
03 / 06
Existing systems
A system that has become difficult to use or maintain does not always need replacing. We review what is working, what is causing problems and what has to continue operating, then agree whether to improve, rebuild or move the affected parts.
Work we can include
Examine the current application, dependencies and workflows to identify the changes that matter most.
Refine interfaces, data structures and difficult-to-maintain code without automatically replacing the whole system.
Update or replace the parts that no longer support the agreed requirements.
Plan how information will be transferred, checked and made available in the replacement.
Prepare testing, deployment and recovery steps around the risks of changing a live system.
We agree continuity and recovery requirements before replacing a live system. The approach depends on what the business can safely change.
04 / 06
Connected systems
Reduce the need to enter the same information in several places or chase the next step manually. We connect the tools you use and automate defined parts of a process, with clear rules for what happens when information is missing or something fails.
Work we can include
Connect customer-management systems, business software, payment services and internal tools where their interfaces and access allow.
Map information between systems and agree how updates, conflicts and duplicate records will be handled.
Move defined tasks, approvals and notifications through the agreed process, retaining human decisions where needed.
Trigger an action when something changes, or run it on an agreed schedule.
Record activity and identify failed or incomplete work, with retry and escalation behaviour appropriate to the process.
05 / 06
Assisted workflows
Use artificial intelligence for a defined task, with clear checks on the output and a person responsible for decisions that matter. We assess the information, tools and risks before building a workflow. Where conventional automation is a better fit, we recommend that instead.
Work we can include
Identify or organise information from approved documents and records, with checks suited to the task.
Help users find and understand information from the sources agreed for the project.
Present recommendations or flags for review rather than silently handing important decisions to a model.
Examine whether the available data supports a useful prediction or analysis task, and test the approach before wider use.
Define access, permitted information, human review and failure handling around the chosen tools.
Outputs can be incomplete or incorrect. We agree what must be checked, who approves it and what the system must not do automatically.
06 / 06
Technical planning
Work out what should be built, what can be bought and what is better left alone before making a large commitment. We review the requirements and existing systems, explain the options and prepare a practical route for the work.
Work we can include
Understand the business process, constraints, existing tools and people who will use or support the system.
Compare a custom solution with available platforms, including the practical implications of each approach.
Set out the components, data flows and system connections needed for the proposed solution.
Separate essential work from later improvements, with dependencies and risks made visible.
Defined reviews and guidance for teams or delivery partners working on an agreed programme.
Practical guidance needed to deliver an agreed project belongs within that project. Sant Advisory is available for separately scoped reviews and independent decision support.
HOW THE WORK RUNS
We agree the important journeys, information and constraints before development. You review the work at planned points, with a clear distinction between the current release and later changes.
Understand the process, people, existing systems and the problem the software needs to solve.
Confirm the functionality, data, responsibilities, price and schedule, including how the work will be tested.
Develop the agreed features, demonstrate progress and check them with the people who need to use the system.
Prepare deployment, check the release and explain the access, documentation and ongoing arrangements.
Before launch, we explain the hosting, monitoring, maintenance and support arrangements appropriate to the system. Access, recovery requirements, third-party costs and future development are addressed in the proposal rather than left for you to work out afterwards.
A completed build does not automatically include indefinite support or new features. We distinguish technical care from further development so you know what continues and what needs another scope.
Explore hosting and careWAYS TO WORK WITH SANT
A software project, ongoing technical care and independent advice are different kinds of work. We explain which are needed and how they fit into the agreed scope.
01
For a new application, integration, product release or improvement to an existing platform. We agree the deliverables, milestones and price, with hosting and ongoing work explained before development starts.
Discuss a software project02
For a website or application that needs hosting, maintenance and technical oversight. Sant Cloud provides care options, with the support appropriate to the system confirmed before it is taken on.
Explore Sant Cloud03
For a platform choice, proposed rebuild or technical decision that needs a considered review. Sant Advisory provides separately scoped guidance without assuming that a development project must follow.
Explore Sant AdvisoryPRACTICAL QUESTIONS
Yes. We begin by reviewing the existing system and the changes needed. The work might be a targeted improvement, an integration, a staged rebuild or a replacement. A complete rebuild is not the automatic recommendation.
No. Start with the problem, who is affected and what you need to work differently. We explain what needs to be clarified before quoting or building. A more involved assessment can be separately scoped when required.
The functionality, existing systems, data and delivery requirements determine the scope. We confirm the price, schedule and what is needed from you before work begins. Third-party services and ongoing costs are explained alongside the build.
Not necessarily. We review the current environment and what is needed to deliver and support the agreed work. Any required hosting change or separate care arrangement is explained before you commit.
Some clearly defined work may fit a dedicated build day. We confirm the outcome, dependencies and preparation first. It is not a promise to build a complex platform in a day. Explore Build in a Day.
Tell us about the process, the tools you use and what needs to change. We will help you define a practical starting point and explain what the next step involves.