Small Pea Software provides focused software services for businesses that need systems tailored to their processes — from bespoke applications and web platforms to integrations and long-term support.
Services Overview
Our services are designed to work together. A typical client engagement might begin with custom software development, include API connections to existing platforms, deploy to a cloud environment, and continue with ongoing maintenance. You can engage us for a single service or for an end-to-end delivery that spans several areas. Each service page on this site describes the scope, typical use cases, and how we approach that type of work in more detail.
We do not sell pre-packaged software licences or force your workflows into a generic product. Every service is delivered against agreed requirements, with clear documentation and handover material so you understand what has been built and how to operate it.
Custom Software Development
Bespoke applications built around your workflows, business rules, and reporting needs. This is our core offering: software designed for how your organisation actually operates rather than how a vendor assumes it should. Custom development covers internal tools, operational systems, workflow engines, and specialised calculators or processors that off-the-shelf products do not provide.
Projects range from focused utilities that replace a single painful manual process to comprehensive platforms that become the operational backbone of a department. We document requirements, agree architecture, and deliver in stages so you can validate direction before the full investment is committed.
Read more about Custom Software Development →
Web Application Development
Secure browser-based systems for staff, partners, or customers. Web applications remove the need for desktop installation and allow controlled access from approved locations and devices. We build responsive interfaces optimised for the way your users work — often desktop-first for internal operations, with mobile-friendly views where field access matters.
Authentication, role-based access, session management, and data validation are built in from the start. Whether the application is internal-only or customer-facing, we apply appropriate security controls and document how access is managed.
Read more about Web Application Development →
API and Integration
Connections between platforms that currently require manual data transfer. We integrate accounting systems, CRMs, inventory platforms, payment gateways, and legacy databases through APIs, scheduled imports, webhooks, or middleware layers. The goal is consistent data across systems without duplicate entry or reconciliation headaches.
Integration work requires careful attention to error handling, logging, and recovery when external systems are unavailable. We design connections that fail gracefully and provide visibility when something needs attention rather than silently corrupting data.
Read more about API & Integration →
Maintenance and Support
Ongoing assistance for systems in production. Support covers defect resolution, security and dependency updates, minor enhancements, and operational guidance. We maintain software we have built and, after review, can take over systems developed elsewhere where the codebase is maintainable and documentation or knowledge transfer is available.
Support engagements are structured with defined response expectations and scope so you know what is included. Work beyond the support scope — new modules, substantial redesign, or major feature additions — is handled as project delivery with separate quoting.
Read more about Maintenance & Support →
Solutions That Extend Our Services
Beyond core development and support, we deliver specialised solution areas that often form part of a larger project: Business Applications for operations and administration, Data & Reporting for dashboards and exports, Cloud Deployment for hosted environments, and Security & Compliance for access control and audit requirements.
How Services Fit Together
Many clients begin with a single pain point — a manual process, a missing integration, an ageing internal tool — and expand over time. A project that starts as custom software development may later add reporting modules, connect to a new accounting platform, or move from on-premises hosting to cloud deployment. Our service structure accommodates that evolution without forcing you into a new vendor relationship at each stage.
When to Combine Services
Not every project needs every service from day one. A standalone API integration between two mature platforms may require only integration work and light maintenance — building a new web application would add unnecessary scope. Conversely, a greenfield operations portal almost always combines custom software development with web application delivery, and often adds data reporting once core workflows are stable.
Combine services when the operational outcome depends on them working together. Customer-facing portals that pull data from a CRM need web applications plus API integration. Regulated environments frequently pair custom development with security and compliance controls from the first design conversation. Cloud deployment belongs in the initial plan when hosting, release management, or data residency are constraints — not as an afterthought once code is complete.
Defer services when dependencies are not yet clear. Reporting dashboards built before transactional workflows are validated often answer the wrong questions. Heavy integration work before system-of-record rules are agreed creates reconciliation debt. We help you sequence services so each phase produces something usable, not a partial system that cannot operate until everything is finished.
Typical Project Sequencing
A common pattern for new operational systems runs: discovery and scope, then core application build, then integrations, then reporting and refinements, then deployment and handover. Integrations are often staged — critical data paths first, secondary feeds in a later phase — so staff can begin using the system before every connection is live.
Legacy replacement projects may invert parts of this sequence. Data migration planning and parallel-running strategy are established early, even when the new interface is built incrementally. Support retainers typically begin at or shortly after go-live, once warranty coverage ends and the system enters daily production use.
The table in the section below illustrates how services commonly combine in practice. Use it as a conversation starter — your constraints will determine the actual sequence. See Our Process for how phases map to delivery milestones.
We build software you can grow into, not software you will need to replace because the original developer cannot support it.
What to Expect When You Engage Us
Regardless of which service you need, the experience is consistent. We communicate in plain language, document decisions, and deliver against agreed scope. You have direct contact with the people doing the work. Quotes are provided before development begins. Source code and deployment material are handed over on completion.
To discuss which services apply to your situation, visit our Engagement Options page or contact us at support@smallpeasoftware.com.
