We transform organisations from the inside out by crafting services, websites and software solutions that build connection.

Most projects fall between $50,000 and $500,000, with four factors driving the range: scope (a single product versus end-to-end transformation), integration complexity (how many existing systems connect in), platform licensing (open-source like Umbraco or Payload versus enterprise stacks like Sitefinity or Microsoft 365), and the ongoing support model. As a rough guide: a corporate website rebuild typically lands at $50k–$120k, an intranet or portal at $80k–$250k, and custom software with multiple integrations at $150k–$500k+. We scope in two stages, a paid discovery that locks requirements, then a fixed price or capped time-and-materials build, so you see the real number before committing to delivery.

Typical timelines: a website rebuild ships in 8–14 weeks, an intranet or portal in 12–20 weeks, and custom software or transformation programs run 4–9 months. We work in two-week sprints and demo working software every fortnight, so progress is visible and re-prioritisation happens early rather than at the end. WA government and enterprise projects usually add 2–4 weeks for security reviews, WCAG 2.1 AA accessibility audits, and procurement steps,  we factor these into the schedule from day one rather than discovering them late..

The right platform depends on what the site needs to do, not what an agency prefers to sell:

• Kentico Xperience by Kentico — marketing-led sites needing personalisation, multi-site management, and a strong page builder for non-technical editors.
• Microsoft SharePoint — intranets where you want deep integration with Teams, Outlook, and existing Entra ID identity.
• Payload CMS — headless, developer-first builds where the site is one of several front-ends (web, mobile, kiosk) consuming the same content.
• Umbraco — open-source .NET CMS with no licensing cost and strong customisability for technical teams.
• Sitefinity — enterprise marketing sites with complex content workflows and integrated digital experience features.

Every project moves through four phases. Pre-flight (1–2 weeks, free) maps your goals, audiences, and constraints into a one-page brief and rough cost band. Discovery (2–6 weeks, paid) runs user research, technical assessment, and content audit, then delivers a fixed scope, design direction, and project plan. Build runs in two-week sprints with fortnightly demos and a shared backlog in Azure DevOps or Jira. Launch and beyond covers deployment, training, a defects-warranty period, and transition into ongoing support if you want it. You're never locked in beyond the current phase,if discovery shows the project doesn't stack up, we'll say so..

Three support tiers, all delivered by a Perth-based team during AWST business hours. Maintenance covers security patching, CMS upgrades, hosting management, and a fixed bucket of small change requests each month. Continuous improvement adds a retained sprint team that ships new features alongside maintenance, used by clients with active product roadmaps. Incident response is 24/7 on-call for production issues with response and resolution SLAs tied to severity. Most sites we build run on Microsoft Azure with monitoring, automated backups, and disaster recovery configured at launch. Around two-thirds of clients move to a continuous improvement retainer within six months because the post-launch insights are usually more valuable than the original launch backlog.

Usually yes. Most useful AI integrations sit alongside your existing systems rather than replacing them. The patterns we deliver most often:

• RAG-based knowledge search over intranets, document libraries, and policy repositories, so staff find answers in seconds rather than hunting through SharePoint or shared drives.
• Embedded copilots in line-of-business apps, built on the Microsoft AI stack (Azure OpenAI, Copilot Studio) or direct API calls to providers like Anthropic, OpenAI, and Google.
• Document processing pipelines that extract, classify, and route forms-heavy work, common for councils, regulators, and service organisations.
• Content workflows inside the CMS, including drafting, summarisation, translation, and accessibility checks.

For Australian government and enterprise clients, all of this can run inside Australian Azure regions to meet data sovereignty requirements. Every AI engagement starts with a 1–2 week feasibility assessment on your real data before you commit to a build , about a third of those end with us recommending against the AI route because a simpler automation gets the same result faster and cheaper. That's the recommendation you won't get from a vendor whose only product is AI.

CMS migrations split into four parallel workstreams: content (extracting, cleaning, restructuring, usually the longest), design (refreshing or rebuilding the front-end on the new platform), integrations (rewiring connections to CRM, payment, identity, or line-of-business systems), and SEO continuity (URL mapping, 301 redirects, structured data, and traffic monitoring through cutover). A typical mid-size migration takes 3–5 months. The two biggest risks are content quality issues surfacing late and SEO traffic loss in the first 90 days post-launch, both mitigated by auditing content in week one and running the new site on a staging URL with full crawl checks before going live. We've delivered migrations across Kentico versions, Sitefinity to Kentico to Umbraco, and on-prem SharePoint to SharePoint Online.

Three mechanisms. First, fixed-scope discovery, we don't quote a build until requirements are locked. Second, fortnightly demos against a transparent backlog, so scope creep gets surfaced and priced before it lands in the work rather than at the end. Third, a single accountable project manager per engagement, not a rotating account team. Change requests get a written impact assessment, what it costs, what it delays, and what it displaces, before work starts. For government and enterprise clients we publish weekly status reports against budget, schedule, and risk register, and run independent quality reviews at major milestones.

We've delivered digital projects for the WA Department of Transport (Main Site and  the Your Move portal), the Department of Water and Environmental Regulation (Microsoft intranet), and the cities of Subiaco, Belmont, Vincent, Cockburn, and South Perth, among others. Public sector work has specific requirements, WCAG 2.1 AA accessibility, IRAP-aligned hosting, procurement compliance under the WA State Supply Commission framework, and the need to serve ratepayers across age and ability, and our team has shipped against all of them. Being in Perth means on-site workshops, stakeholder sessions, and steering committees happen without travel costs or eastern-states timezone friction.