48SouthEast
We design and build software for organisations that need dependable systems. Our work includes:
Full applications and internal platforms
Platform rewrites and stabilisation of existing systems
Prototypes intended to become real products
Smaller systems that replace manual or spreadsheet-driven workflows
Most projects involve operational software, data-heavy systems, or platforms that need to remain stable as requirements evolve. We work across the stack and take responsibility for how systems behave once they are in use.
What we do not do
We do not operate as a staff augmentation shop
We do not sell generic development capacity
We do not take on poorly defined work driven by unrealistic timelines
Our work spans building, leading, and maintaining production software over multiple years, across different domains and organisational contexts.
Systems and products
Business management and SaaS platforms used as core operational software
Ecommerce and marketplace systems, including reseller detection and auditing tools
Internal platforms and dashboards replacing spreadsheet-driven processes
Data ingestion and automation services, including real-time scraping and API-driven systems
Developer-facing tooling, including maintained open-source libraries used outside our own organisation
Scale and operational demands
Platforms used daily by tens of thousands of active users
Systems handling large volumes of transactional and operational data
Software where uptime, correctness, and traceability mattered
Codebases that evolved across multiple product cycles
Who we have worked with
Venture-backed and bootstrapped product companies where software was the core business
Product teams responsible for revenue-generating SaaS and marketplace platforms
Founders and CTOs making architecture and delivery decisions under real constraints
Engineering teams distributed across multiple countries and time zones
Operations and business teams relying on internal systems for daily decisions
Organisations handling sensitive, user-linked, or audit-relevant data
Non-profit and mission-driven organisations with reporting and accountability requirements
How we were involved
Leading engineering teams, code review, and technical decision-making
Owning core platform components rather than isolated features
Designing system architecture and delivery approaches
Maintaining and supporting live systems already in active use
Writing documentation and supporting knowledge transfer
Working closely with non-technical stakeholders alongside engineers
Delivery context
Many systems were already in daily use when we took responsibility
Changes were made in live environments where errors had downstream impact on revenue, reporting, or external users
Work was carried out in direct collaboration with founders, CTOs, and operations leads, without layers of account management
This includes both greenfield builds and stepping into existing systems to stabilise, extend, and operate them over time.
We tend to work best with small to mid-sized teams that have a clear problem to solve and can make decisions as the work progresses.
Clients often come to us when something matters enough to get right, but not enough to justify a large vendor. Organisations that value clarity, realistic planning, and long-term maintainability usually find the process straightforward.
We are likely not a good fit if speed is prioritised over correctness, or if the brief is still largely hypothetical.
Alongside client work, we’re currently developing a legal research and drafting tool.
The work focuses on:
Ingesting large volumes of court documents
Extracting usable text from inconsistent formats
Organising material in ways that reflect how legal professionals search and read
Supporting drafting workflows through reusable legal structures
The system is in active development. Core components are already in use. We are preparing for an initial launch.
Most projects start with a short discussion to understand what is required and what constraints matter.
From there, we define a practical scope and begin building without extended lead time. Work is delivered in small increments, with regular updates based on what exists rather than abstract plans.
Engagements usually begin as scoped projects. Some clients continue with us for ongoing improvements, maintenance, or additional work once a system is live.
Scope, responsibilities, and handover are agreed before work begins.
Our team works across time zones with deliberate overlap for Australian and US business hours.
Communication is handled through a small number of agreed channels, with clear points of contact throughout a project. Contracts, invoicing, and communication follow standard Australian and US business practices.
All client work is governed by written agreements that define scope, ownership, and responsibilities clearly.
Intellectual property created during client engagements remains with the client, as defined in the relevant agreements.
Our baseline approach includes:
Confidentiality as a standard requirement
Access limited to what is required for delivery and support
Careful credential management
Separate environments where appropriate
Access removed once work concludes
If you would like to discuss a project, email: charles@48southeast.com and include a brief description of what you are trying to build or fix.
The first conversation is informal and focused on fit. If it is not a fit, we will say so quickly.