SOCO Corporation Ltd (ASX:SOC): FY26 Contract Wins and Earnings Pressures
SOCO booked more than $24 million in FY26 contracts, but the numbers still need watching
SOCO Corporation Ltd entered contracts worth more than $24 million during the financial year ended 30 June 2026. That sounds strong. It is also only part of the story.
The Microsoft-solutions and IT consulting company reported revenue of $20.624 million, down 3.1% from FY2025. Gross profit moved in the right direction, rising 2.6% to $5.284 million, and gross margin improved from 24.2% to 25.6%.[1]
But SOCO still reported a full-year underlying EBITDA loss of $0.43 million. The second half was better, with underlying EBITDA turning positive at $0.22 million after a $0.64 million loss in the first half.[2]
For a small business owner, this is not a reason to panic. It is a reason to ask better questions before signing a large project.
Why the $24 million contract figure is not the same as $24 million in revenue
Contracts create future work. They do not automatically create completed projects, collected cash, or healthy profit.
About $9.5 million of contracted project value carried into FY2027 for mobilisation and delivery.[1] That gives SOCO a useful starting point for the new financial year, but delivery still has to happen. Staff must be available. Project scope must stay under control. Customer decisions cannot sit idle for months.
That distinction matters for a company buying a Microsoft 365 migration, business application, cloud project, or integration. A provider can have a full sales pipeline and still struggle with scheduling or execution.
We would not read the contract number as proof that every customer will receive perfect service. We would read it as evidence that demand exists, paired with a reminder to check how the provider runs projects after the contract is signed.
What SOCO’s earnings pressure means for customers
SOCO’s revenue fell even though gross profit and margin improved. The company also moved from a prior-year underlying EBITDA profit of $0.21 million to a FY2026 loss of $0.43 million.[1]
The first half was affected by delayed project mobilisation and lower utilisation, while the second half improved.[1] The linked reporting does not make every cause of the earnings pressure clear, and it does not identify each customer or contract value. That uncertainty should stay on the table.
For customers, financial pressure can show up indirectly. A provider may assign fewer senior people to a project. It may push for faster invoicing. It may rely more heavily on subcontractors. None of those things is automatically bad, but each deserves attention before work begins.
We would ask who will actually deliver the project, how many hours are committed, and what happens if the assigned consultant leaves. We would also insist on named milestones rather than a broad promise to “modernise” the business.
What we would check before signing a project
SOCO’s results do not change the basic buying process. They make the process more important.
First, separate recurring support from project work. A business needs to know who handles an urgent Microsoft 365 issue after the implementation team moves on.
Second, put acceptance criteria in writing. A completed migration should define which users, devices, applications, permissions, and data have been moved and tested.
Third, ask for a delivery schedule that includes customer dependencies. If the provider needs a decision from your staff, the project plan should show it. Otherwise, delays become arguments about who was waiting for whom.
Fourth, confirm where documentation will live. Password procedures, diagrams, configuration notes, and recovery steps should not remain in one consultant’s notebook.
Finally, review payment terms against completed work. A large deposit can be reasonable for a complex project, but the payment schedule should still track measurable progress.
Our read for a 30-person company
This is not a headline that should make a 30-person company abandon SOCO. It also is not a reason to assume that a strong contract pipeline guarantees stable delivery.
The positive signal is the improved second half and the $9.5 million carried into FY2027. The concern is that full-year profitability remained negative, while revenue declined. Those facts point to a provider with work available but execution and cost control still under pressure.
We would keep the shortlist open, then test the provider with a tightly defined first phase. Start with an assessment, a limited migration, or a documented improvement project. Set a clear completion test. Keep support coverage separate from project promises.
If you are reviewing SOCO or another IT provider, ask for a written delivery plan and a named escalation contact before approving the next project. IT911Now can help you compare the plan against the risks your business can actually afford.
