Small Pea Software is an Australian custom software company established in 2022 and based in Chatswood, NSW. We design and build business applications, web platforms, and integrations for organisations that need dependable systems, clear communication, and direct access to the people doing the work.
Who We Are
Founded in 2022, SMALL PEA SOFTWARE PTY LTD develops software for businesses that have outgrown spreadsheets, disconnected tools, or rigid off-the-shelf products. Our work centres on practical outcomes: fewer manual steps, clearer records, and systems that staff can rely on every day. We are not a product vendor selling a one-size-fits-all platform. Each engagement is shaped around your workflows, your data, and the constraints of your existing environment.
Clients come to us when they need a partner who will listen carefully, document requirements in plain language, and deliver maintainable code rather than a short-term fix. Whether the project is an internal operations portal, a customer-facing web application, or a connection between two platforms that do not currently talk to each other, we approach it with the same discipline: understand the problem first, agree the scope clearly, then build with care.
How We Approach Software Delivery
Good software is not only about features. It is about whether the system remains understandable six months after launch, whether your team can use it without constant workarounds, and whether you can get help when something needs adjusting. We structure projects so that design decisions, data models, and delivery milestones are visible throughout — not buried in technical jargon or left until the final week.
Our development practice emphasises readable architecture, sensible documentation, and testing of the paths that matter most to daily operations. We choose technologies for reliability and long-term maintainability, not for novelty. When we recommend an approach, we explain why it fits your situation and what trade-offs it involves, so you can make informed decisions alongside us.
We believe the best software partnerships are built on clarity: clear requirements, clear communication, and clear accountability for what is being delivered and when.
What We Build
Our work spans several areas that often overlap in a single project. Custom business applications capture operational workflows — requests, approvals, scheduling, inventory movements, and internal administration — in one coherent system. Web applications give staff, partners, or customers secure browser-based access without installing desktop software. Integration layers connect accounting, CRM, inventory, or legacy databases so data does not need to be re-entered by hand.
- Internal operations portals and staff-facing web systems
- Customer account portals, service records, and document access
- Workflow applications with approvals, notifications, and audit trails
- Dashboards, exports, and reporting built from your operational data
- API connections and middleware between existing business platforms
- Ongoing maintenance, fixes, and incremental improvements after go-live
Requirement-Led, Not Template-Led
We do not start from a generic product and try to bend your processes to fit it. We start from your brief — or help you shape one — and design software that reflects how your organisation actually operates. That sometimes means a focused tool that does one job well. At other times it means a broader platform that replaces several disconnected processes. In every case, the scope is documented before significant development begins.
Australian Business, Direct Contact
Small Pea Software is based at Level 4, 8 Thomas St, Chatswood NSW 2067 and serves clients across Australia who value local accountability. You communicate directly with the people building your software — by email at support@smallpeasoftware.com or by phone on 02 4404 1725. There is no opaque hand-off to an offshore team or an account manager who cannot answer technical questions.
Security, Privacy, and Compliance
Access control, data handling, and deployment practices are considered from the first design conversation, not added as an afterthought. We work with clients who need audit trails, role-based permissions, and sensible handling of personal or commercially sensitive information. Where your industry or internal policies impose specific requirements, we incorporate those into the architecture and documentation from the outset.
Our Privacy Policy describes how we handle personal information in the course of our work. For systems we build on your behalf, we align with your data governance expectations and document how information flows through the application.
Working With Us
Most new relationships begin with a conversation about what you are trying to achieve, what tools you use today, and what constraints — budget, timeline, technical, or regulatory — apply. From there we can outline a scope, propose an engagement model, and agree next steps. You can read more about our delivery approach on the Our Process page and about engagement options on the Engagement Options page.
If you have an existing system that needs improvement, extension, or integration with other platforms, we are equally comfortable picking up work mid-stream — provided we can review the current codebase, understand the architecture, and agree a sensible path forward. We do not promise unrealistic timelines or scope we cannot stand behind. What we do promise is honest communication and software built to last.
Quality Standards and Documentation
Quality for us means software that behaves predictably under real operating conditions — not a checklist of buzzwords. We test the workflows staff use daily, validate integration error handling when external systems fail, and review access controls against agreed role definitions. Code is structured for readability: clear module boundaries, sensible naming, and comments where business logic is not self-evident from the code alone.
Documentation is a deliverable, not an afterthought. Scope records capture what was agreed. Architecture notes explain how components connect and why key decisions were made. Handover material covers deployment steps, environment configuration, and operational procedures your staff or IT provider will need after launch. The goal is that someone unfamiliar with the project can understand the system six months later without reconstructing context from memory.
Client Communication Rhythm
Communication cadence is agreed during scoping and adjusted if the project needs change. Typical project delivery includes written progress updates at milestone boundaries, prompt notification when a dependency or blocker arises, and scheduled review sessions when working software is ready for feedback. We do not flood you with daily noise, but we do not disappear for weeks either.
You have direct contact with the people doing the work — by email at support@smallpeasoftware.com or by phone on 02 4404 1725. Questions receive substantive answers, not deflection to a ticket queue. Decisions that affect scope, timeline, or architecture are documented in writing so both sides share the same record. That rhythm continues through warranty and, if engaged, into ongoing support.
Ready to Discuss Your Requirements?
Tell us what you need to build, replace, or connect. We will respond with practical next steps and an outline of how we can assist. Visit our contact page or email support@smallpeasoftware.com to start the conversation.
