Small Pea Software offers structured engagement options to match how you want to work — whether you need a defined project delivered end to end, ongoing support for systems already in production, or technical consulting to plan your next initiative.
Choosing the Right Engagement
Not every software need fits the same commercial model. A greenfield application with clear requirements suits fixed-scope project delivery. A system already in daily use may need a support arrangement rather than a new build. A leadership team planning a major platform investment may benefit from consulting before committing to development. We help you select the model that fits your situation and explain how pricing, timelines, and deliverables work under each option.
All engagements begin with a conversation. There is no obligation to proceed beyond an initial discussion. If we are not the right fit — because of timing, scope, or technical requirements — we will say so plainly rather than take on work we cannot deliver well.
Project Delivery
Project delivery is our primary model for building new software or delivering a substantial new module to an existing platform. Scope, deliverables, milestones, timeline, and price are agreed in writing before development begins. Payment is typically structured around milestones — for example, upon completion of design approval, mid-build review, and final delivery — so that progress and investment align.
This model suits clients who know what they need (or are willing to define it through a discovery phase) and want a clear endpoint: a working system, tested and deployed, with handover documentation. It includes a post-launch warranty period covering defects in delivered functionality.
What Project Delivery Includes
- Scope document with deliverables, assumptions, and exclusions
- Design and architecture approval before full build
- Staged development with review checkpoints
- Testing, deployment assistance, and handover documentation
- Warranty period for defects in agreed deliverables
Ongoing Support
Systems in production need continued attention. Dependencies age, browsers change, security patches appear, and business requirements evolve. Our support engagements provide a defined channel for issue reporting, bug fixes, minor enhancements, and operational guidance for software we have built or systems we have taken over after review.
Support is structured as a retainer or agreed monthly allocation of hours, depending on your anticipated needs. Priority response times and scope of included work are documented so you know what to expect. Larger feature development beyond the support scope is quoted separately as incremental project work.
When Support Makes Sense
Support engagements suit organisations that have gone live with custom software and want a reliable partner for fixes and small improvements without renegotiating every request. They also suit clients transitioning from another developer where we first conduct a codebase review to ensure we can maintain the system responsibly.
Consulting
Consulting engagements provide technical advice without necessarily committing to a full build. Typical uses include requirements review before a major procurement decision, architecture assessment of an existing or proposed system, vendor evaluation support, implementation planning, and documentation of technical recommendations for internal stakeholders.
Consulting is billed on a time-and-materials basis or as a fixed fee for a defined deliverable — such as a written assessment or implementation roadmap. It can stand alone or precede a project delivery engagement if the output of consulting is a specification ready for development.
We would rather help you make a sound decision before you spend heavily on development than rush into a build that does not match your needs.
Commercial Terms
Pricing depends on scope, complexity, integration requirements, and timeline. We provide written quotes before work begins. Invoices are issued in Australian dollars. Payment terms are stated on each invoice. For project delivery, milestone payments are tied to agreed deliverables rather than calendar time alone — so you pay for completed stages of work.
Intellectual property in custom software developed for you is typically assigned to you upon final payment, unless otherwise agreed in writing. We retain the right to use general know-how, techniques, and non-client-specific components. Source code, deployment credentials, and documentation are handed over as part of project completion.
Payment Milestones, Changes, and Ownership
Project delivery engagements are structured around agreed milestones — commonly design approval, mid-build review, and final delivery — with invoices issued when each milestone's deliverables are met. Milestone definitions are documented in the scope so you know what triggers each payment. We do not invoice for work that falls outside agreed deliverables without prior written approval.
Change requests are a normal part of software delivery. When you ask for functionality outside the agreed scope, we assess impact on timeline and cost and provide a written change quote before proceeding. Minor adjustments that do not materially affect deliverables may be absorbed within the project; substantial additions are priced separately. This keeps invoices predictable and scope transparent.
Intellectual property in bespoke software developed under project delivery is assigned to you upon final payment, unless otherwise agreed. You receive source code, deployment documentation, and credentials needed to operate independently. We retain the right to reuse general techniques and non-client-specific components. Third-party libraries and services remain subject to their respective licences, which we document at handover.
Project delivery includes a post-launch warranty period — typically thirty days — covering defects in functionality delivered under the agreed scope. The warranty addresses correction of agreed behaviour, not new features or changes arising from altered business requirements. Beyond warranty, ongoing maintenance and support arrangements provide a defined channel for fixes, updates, and incremental improvements.
Getting Started
The fastest way to begin is to describe your situation: what you need built or improved, what systems you use today, your approximate timeline, and any budget range you are working within. That context allows us to suggest the most appropriate engagement model and outline next steps. You can use the form on this page, email support@smallpeasoftware.com, or call 02 4404 1725.
