Services
Transform ideas into secure, cloud-based applications.
Whether you are replacing spreadsheets, streamlining business operations, creating a customer portal, supporting field teams, or bringing a new software product to market, XLS Experts designs and builds modern web applications that work anywhere, on any device, for multiple users—with one live source of data, cloud hosting and architecture shaped around your actual requirements.
Looking for all services or enterprise Excel applications?
Historically, custom software development was often slow, expensive and difficult to prototype. It was frequently restricted to large organisations with substantial budgets and internal IT teams. That picture has changed.
Modern frameworks, reusable cloud services and AI-assisted development have made custom web applications more accessible to ordinary businesses. Ideas can be prototyped quickly, working software can be demonstrated early, and managed cloud infrastructure can replace the need to build every component from scratch.
At XLS Experts, AI-assisted development—using Cursor as our development environment—helps experienced developers work faster, prototype more effectively and devote more time to business logic, user experience and testing. It does not replace software engineering. It supports it.
The practical result is that custom software can now be viable for projects that would once have been cost-prohibitive. A business does not need to commission a massive platform in its first phase. A focused first version—sometimes described as a minimum viable application—can prove the process, then expand as requirements mature.
Visitors arrive with different starting points: an entirely new application idea, a proposed SaaS product, a customer-service concept, a mobile or field requirement, an operational bottleneck, a spreadsheet-based system that has reached its limit, or a mix of spreadsheets, email, shared drives, paper forms and disconnected software. Custom web application development NZ engagements often begin by clarifying which of these pathways is actually in front of the business—and which parts of the process should stay in Excel for modelling and analysis.
A web application is software accessed through a browser rather than being installed as a traditional desktop program. Users sign in, work with live data and complete business workflows from devices that have an internet connection and the right permissions.
Primarily publishes information—pages, content and marketing. Interaction is limited compared with an operational system.
Supports interactive work: authentication, data capture, business rules, workflows, reporting and integrations.
Powerful for analysis and modelling, but weaker for concurrent multi-user operations, customer access and centralised deployment.
A responsive web application can often work across desktop, tablet and mobile without separate native apps. Native apps are still appropriate in some cases. A SaaS platform is software sold or licensed to multiple customers—often built as a web application.
Browser-based, cloud-hosted applications excel where Excel is weakest: concurrent multi-user work, any-device access and a single live source of operational data. Excel remains excellent for analysis, modelling, flexible reporting, scenario work, financial calculations and specialist power users. Each platform has an appropriate role.
Users can securely access the application wherever they have an internet connection and appropriate authorisation.
Desktop, laptop, tablet or mobile browser—without requiring a separate native app for every role.
Multiple users can work in the application at the same time without passing files around or overwriting one another’s changes.
Everyone works with the same current information rather than competing versions of a workbook.
Different users see and edit only what is relevant to them—staff, managers, contractors, customers or partners.
Important actions, changes and approvals can be recorded so processes remain reviewable.
Updates can be released centrally instead of installing software on each device.
The underlying platform can expand as usage, data volumes and user numbers grow.
Applications can connect with spreadsheets, accounting systems, APIs, databases, email services and other business tools.
External parties can interact securely without gaining access to internal files and networks.
Related: Enterprise Excel applications · Dashboards & Business Intelligence
Custom web application development for New Zealand businesses often starts with a familiar operational pattern: a process that has outgrown email, paper, shared drives or disconnected spreadsheets—or a new idea that needs a secure multi-user home.
If one of these patterns sounds familiar, we can help assess whether a focused web application, hybrid system or governed spreadsheet is the practical next step.
For now, all web application services sit on this page. The structure below makes it easy to expand into dedicated pages later for business apps, customer-facing apps and SaaS products.
Internal operational applications used by staff, management, contractors and business partners. These systems formalise how work moves through the organisation—capturing data once, applying business rules consistently and giving the right people visibility at the right time.
Externally facing applications used by customers, members, policyholders, suppliers, tenants, contractors or the public. They provide secure, branded access without exposing internal files, networks or uncontrolled spreadsheets.
Software intended to be sold or licensed to multiple customers. We can help with product discovery, prototypes, authentication, account structures, subscriptions or usage models where required, multi-tenant architecture, scalable databases, administration tools, reporting and staged product development.
These areas often overlap. An internal business application may later become a SaaS product once the workflow is proven.
Business understanding first. Technology second. Architecture chosen for the problem—not the other way around.
Many effective applications begin as spreadsheets. Spreadsheets allow a knowledgeable person to develop and prove formulas, calculations, processes, reports, data structures, workflows and business rules. That is a genuine strength—not a weakness.
The problem arises when the workbook must support many simultaneous users, field teams, customer access, mobile devices, secure permissions, high data volumes, audit trails, integrations, automated workflows or centralised live data. At that point, spreadsheet migration to a web application becomes one important pathway—not the only pathway, and not an automatic goal.
XLS Experts can improve the existing spreadsheet, govern and stabilise it, connect it to a database, add a browser-based front end, retain Excel for reporting, or migrate the full operation into a web application. The right choice depends on users, risk, cost and how the process actually works.
Appropriate when the workbook still fits the user group, volumes and collaboration model.
Strengthen structure, validation, performance and documentation so the existing tool remains reliable.
Appropriate when Excel remains the right interface but needs engineering discipline.
Controlled inputs, protected logic, testing, documentation, version management and supportable code.
Appropriate when operations need a browser interface while analysis stays in Excel.
A shared database or API layer supports web capture and workflows, with Excel retained for modelling and reporting.
Appropriate when multi-user access, mobile use, permissions, customers or scale require a browser-first system.
The operational system of work lives in the web application, with Excel optional for specialist analysis.
Related: Governed Excel applications · Excel VBA/Macro Development · Process automation
Hybrid architectures differentiate XLS Experts from generic application developers. We do not assume every calculation must leave Excel—or that every operational process must stay there.
Use each platform for what it does best.
Typical hybrid patterns include field teams capturing data through a browser, customers submitting requests through a portal, operational staff managing workflows in the web application, and managers or analysts using Excel against the same governed data. Scheduled exports can feed existing reporting models; Excel templates can generate specialist documents; the web application controls access and the central database.
Related: Excel Integrations (SQL, API, etc.)
The examples below illustrate the kinds of business web applications, customer-facing tools and hybrid Excel systems we design. Where project details are confidential or still being shaped, capabilities are described carefully as indicative rather than confirmed feature lists.
Named public examples retain facts already published on the XLS Experts site.
Bring your idea, screenshots, spreadsheet, process notes or current frustrations—we will help identify a practical next step.
XLS Experts is not merely a generic web development agency. We combine detailed business-process understanding, more than 20 years of spreadsheet and operational application experience, financial modelling and data expertise, workflow and reporting knowledge, modern web application development, cloud databases and infrastructure, and rapid AI-assisted development using Cursor.
Many web developers can write software. Far fewer can examine an existing operational process, understand the calculations, reporting, workflows, approvals, exceptions and business rules, and then turn that knowledge into a practical working application.
We analyse how work actually moves through a business, including exceptions, dependencies, approvals and reporting requirements.
If the application begins in Excel, we can interpret and preserve the business knowledge embedded in formulas, macros, models and reporting structures.
We have extensive experience with data structures, validation, reporting, dashboards and analysis.
Modern development allows stakeholders to see and test the application early—reducing ambiguity before full delivery.
We work directly with owners, managers, finance teams, operational staff and subject-matter experts—not only IT departments.
A focused first release can be extended as requirements mature, rather than forcing a single large build.
We do not recommend a web application when a governed spreadsheet or smaller automation would solve the problem more economically.
Technology serves the application—not the other way around. We select the architecture according to the application, its users, security requirements, expected scale, integrations and the client’s existing technology environment.
Cursor is our AI-assisted development environment. It is not a JavaScript framework. Next.js and React are web development technologies used in many of our modern applications.
Not every application uses every technology listed. We previously developed applications using Microsoft .NET and SQL-based architectures and can support or integrate with Microsoft environments where appropriate.
Modern applications may include AI-supported capabilities where they deliver practical value. Important decisions may still require human review. We do not promise fully autonomous systems.
AI should be applied carefully—supporting document handling, classification, search, drafting and workflow assistance rather than replacing accountability for business-critical outcomes.
Exact security requirements depend on the sensitivity of the data, user types, client IT policies, industry obligations, application risk and hosting environment. We do not claim formal certifications that XLS Experts does not hold. We do design practical controls that match the risk of the application.
Sign-in, user roles, permissions and user deactivation so only authorised people can see or change relevant data.
Secure cloud hosting, with separation of development and production environments where appropriate, and client-owned cloud environments where required.
Database access controls, encrypted connections, backups, data validation and privacy considerations aligned to the sensitivity of the information.
Audit records for important actions, secure integrations and clear access management as people join or leave the organisation.
A web application does not need to stand alone. Integrations can be assessed or implemented where suitable—depending on available APIs, permissions, licensing and the quality of the source system. We do not claim a completed integration with every named platform.
Feasibility is confirmed during discovery. Sometimes structured file exchange is the practical first step; sometimes a direct API connection is available and appropriate.
Application development is collaborative. Important business rules are often uncovered and refined while users interact with working versions—not only from a written specification.
Enough of the application for stakeholders to understand how it will work in practice.
We can map your idea, users and constraints into a practical first release—without requiring a massive platform on day one.
Many clients worry about risk and cost. A project can begin with one key workflow, one user group, one business unit, one portal, one field process, one reporting requirement or one prototype—then expand after validation.
Possible staged development includes:
Starting small reduces perceived risk. It also produces earlier feedback from real users, which usually improves the quality of later stages.
A focused internal application can be very different in scope from a customer-facing SaaS platform. Cost is driven by complexity and risk—not by marketing packages.
An initial consultation helps identify whether the idea is suitable for a web application, better addressed through Excel or automation, suitable for staged development, or dependent on further technical discovery. We do not publish fixed “apps from $X” pricing, because meaningful estimates require understanding the process.
XLS Experts works with organisations throughout Auckland, Wellington, Christchurch, Hamilton, Tauranga and other regions of New Zealand. This page is currently intended primarily for the New Zealand market—supporting strong local relevance for custom web application development NZ searches while remaining useful to any visitor evaluating a practical delivery partner.
Projects are commonly delivered through a combination of remote workshops, screen sharing, regular demonstrations, online testing and structured review sessions, with onsite work where appropriate. Distance does not prevent clear collaboration when demos and feedback loops are regular.
Concise answers to the commercial and technical questions New Zealand businesses commonly ask about custom web application development.
A web application is software accessed through a browser rather than installed as a traditional desktop program. Users sign in, work with live data and complete workflows from devices that have an internet connection and the right permissions.
A website primarily publishes information. A web application supports interactive work—logging in, capturing data, applying business rules, managing workflows, generating outputs and integrating with other systems. Many modern sites include application features, but the purpose and complexity differ.
Often yes, where the spreadsheet already encodes a proven process. We assess the calculations, workflows, users and risks, then recommend improving the spreadsheet, governing it, building a hybrid solution, or migrating the operation into a full web application.
Yes. A common pattern is a web application for multi-user operations, with Excel retained for analysis, modelling or specialist reporting against the same governed data.
When you need concurrent multi-user editing, field or customer access, strong role-based security, mobile-first workflows, higher data volumes, audit trails or integrations that workbooks struggle to support reliably. We help decide based on users, risk and cost—not a default rebuild.
Yes. True multi-user operation is one of the main reasons organisations choose a web application. Multiple authorised users can work against one live dataset without emailing files or overwriting each other’s changes.
Responsive web applications are designed to work across desktop, tablet and mobile browsers. Native mobile apps are sometimes still appropriate, but many operational needs can be met with a well-designed browser application.
Yes. Customer and supplier portals are a common category of web application—providing secure external access to selected workflows without exposing internal networks or uncontrolled files.
Yes. We can help design and build software intended for multiple customers, including authentication, account structures, multi-tenant architecture, administration tools and staged product development. Scope and commercial model are agreed during discovery.
Yes. Early prototypes and working releases help validate workflows, interfaces and assumptions before wider investment. Many projects begin with a focused first version rather than a complete platform.
Timelines depend on workflows, roles, integrations, data migration and the breadth of the first release. A focused operational application can be delivered in stages; a multi-tenant SaaS product typically takes longer. Discovery produces a realistic delivery plan.
Cost depends on scope: workflows, roles, data model, integrations, interface complexity, mobile or offline needs, reporting, security and ongoing support. A focused internal application differs substantially from a customer-facing SaaS platform. An initial consultation clarifies suitability and likely staging.
Our modern stack commonly includes Next.js, React, TypeScript, Node.js and cloud platforms such as Google Cloud, Firebase, Firestore, Supabase and PostgreSQL. We previously developed applications using Microsoft .NET and SQL architectures and can support or integrate with Microsoft environments where appropriate. Cursor is our AI-assisted development environment—not a JavaScript framework. Architecture is selected for the application, users, security, scale and existing systems.
Hosting is selected to suit the project—commonly managed cloud platforms such as Google Cloud or equivalent environments. Exact hosting, ownership and operational arrangements are agreed as part of the project proposal.
Often yes, where that aligns with your IT and security requirements. Client-owned cloud environments can be used where appropriate and are discussed during architecture planning.
Integration can be assessed where suitable APIs, permissions, licensing and data quality exist. Potential connections include Excel, Microsoft 365, Google Workspace, accounting platforms, CRM systems, email, payments, mapping services, databases and other external APIs.
Often yes. We can review an existing codebase or partial build, assess maintainability and risk, and recommend remediation, completion or a controlled rebuild where that is more practical.
Where it delivers practical value—such as document extraction, classification, summarisation, search assistance or drafting support. Important decisions may still require human review. We do not promise fully autonomous systems.
Ownership, hosting, licensing and support arrangements are agreed as part of the project proposal. Commercial terms are set out clearly before development proceeds.
Support, enhancements, monitoring and documentation updates can be arranged according to the importance of the application and expected change. Details are agreed in the proposal rather than assumed as a fixed package.
Offline capability is possible in some applications, but it adds architectural complexity and must be assessed early. Many field scenarios work well with a mobile-friendly online application; true offline sync is scoped only where needed.
Applications are designed with authentication, roles and permissions so users see and edit only what is relevant. Access management—including deactivating users—is part of operational governance.
No. A clear initial scope helps, but important business rules are often refined while users interact with working versions. We typically progress from discovery into prototype and iterative development rather than requiring a perfect specification first.
Yes. Many commercial products begin as an internal operational application. Once the workflow is proven, multi-tenant accounts, billing and product packaging can be introduced in later stages.
No. Off-the-shelf software is often the right choice when it fits closely. Custom development makes sense when your process, integrations or competitive product requirements are not well served by standard packages—or when a focused custom system is simpler than forcing an unsuitable platform.
A web application may begin as a new software concept, an operational bottleneck, a customer-service opportunity, or a spreadsheet that can no longer support the way the business has grown.
We can help determine the most practical next step—whether that is improving the existing spreadsheet, creating a hybrid system, developing a focused web application, or planning a broader SaaS platform.
Bring your idea, screenshots, an existing spreadsheet, process notes, example forms, current frustrations, and desired users and outcomes.
Big or small, we are happy to discuss it. Send us a message or book a free discovery call — we typically respond same business day.
We review your enquiry carefully and reach out personally — usually same business day. No obligation, no hard sell.
We clarify scope, then provide a clear fixed-price quote and realistic delivery timeframe so you know exactly where you stand.
Once agreed, we build in stages, keep you updated, and hand over a solution your team can rely on — with support if you need it.