Executive summary

Software Cowboy at a glance

We build platforms that connect the software a business already uses and automate the admin in between, so its people can get on with running it – without extra headcount, errors or waiting.

  1. What we build

    We connect the CRM, scheduling, inventory and accounting tools a business already pays for. Information is entered once and arrives wherever it’s needed.

  2. Who it’s for

    Businesses that run on real-world operations: crews, customers, schedules, stock and paperwork. Across the energy industry, from the Davids to the Goliaths.

  3. The outcome

    Quotes, paperwork and follow-ups run as automated flows. People step in only for final checks, exceptions and the decisions that need a person.

  4. How we work

    Plain screens and predictable logic. Anything irreversible is previewed, confirmed and recorded. One team owns the work from design to support.

  5. Security first

    Least access, encryption by default, a clear audit trail and data hosted in Australia, with scheduled patching and a plan for the bad day. We build to the Essential Eight as a minimum.

  6. AI, honestly

    We use AI to research and to challenge our thinking. It sharpens the engineering; it never replaces it.

Tested to completion.

If it isn’t tested to completion, including the edge cases, it doesn’t work yet. It’s the opposite of Schrödinger’s cat: if not tested, it doesn’t work (the cat is dead).

  • 75–80%+of functions covered by test classes, edge cases included
  • QA and UATquality assurance and user acceptance testing before release
  • Sandboxesseparate environments for development, nothing built in production
Dylan Summerville

About Our Founder

Dylan Summerville

Founder and Principal Engineer

Self-taught; built the platforms an energy business runs on, end to end. 10,200+ automated tests, 16+ platforms connected, 4,500+ hours of manual work replaced. Full record at dylansummerville.com.

Where we are

  1. Now

    Mapping the network: what connects to what, and why.

  2. Next

    Planning the security, the architecture and the deployment, before a line of code depends on them.

  3. Then

    Writing the code, with announcements planned for later this year.

Earlier platforms are built and wait for release at a sensible price that scales with the customer. The network is new work.

Follow the work

Follow us on LinkedInClick Here

Read the full site