Regan Behrendorff / Brisbane-based independent developer

I help service businesses and SaaS teams fix fragile workflows.

Bring me a rough product idea, an app that needs fixing, or software the business has outgrown. I work with founders and operators to work out what to build.

New productsExisting appsInternal softwareAI where it fits

$200k+ earned on Upwork / 100% Job Success / 4,455+ paid development hours

If the brief is rough

If you know what needs building, I can start there. If not, I will ask questions, make a first pass, and check it with you in working software.

01

Work out what is not clear

02

Get one useful path working

03

Test it, deploy it, and fix what breaks

A product idea

Work out what the first version needs to do, then build it.

An app that needs attention

I look at the code and releases first, then fix what is stopping progress.

Software that no longer fits

Build the missing tools and connect the systems that already work.

How I work

I make the technical calls and stay with it through release.

First I work out what the software needs to do. Then I build, test, deploy, and hand it over.

The usual steps

Starting rough is fine
01

Work it out

Find what is missing

02

Build

Get one path working

03

Release

Test and get it live

A working first version gives us something real to test before more code depends on it.

01

Start before the whole spec is written

02

Get something real to review early

03

Check edge cases and deployment before handover

$200k+
Upwork earnings
100%
Job Success Score

Where I can help

It might start with a rough idea, an app that needs fixing, or work the current software does not handle.

01

New products and AI features

Start with the idea, work out what it needs to do, then build a first version.

  • ▸Work out the main user and job
  • ▸Build the application or AI feature
  • ▸Test it with the people who will use it
02

Taking over an existing app

I read the code and release process first, then fix what is stopping progress.

  • ▸Find what is making changes difficult
  • ▸Fix the issues blocking the next release
  • ▸Test, deploy, and hand over the work
03

Software for business operations

When the current tools no longer fit, I build the missing software and connect what already works.

  • ▸Internal apps and service portals
  • ▸APIs, Microsoft 365, and data connections
  • ▸Checks for errors and ways to recover

What you can expect to leave with

A first version to tryChanges to an existing appSoftware for day-to-day workA connection between existing systemsAI checked by a personTesting before a releaseHelp getting the app liveNotes for whoever maintains it next

Selected work

Work shown through the problem it solved

Here is what was going wrong, what I did, and what I can share. Some client details need to stay private.

New productsExisting appsBusiness softwareAI and integrations
01

Case 01

Field Operations System
Production workflow

Construction Compliance Platform

A production-grade checklist and evidence workflow connecting field inputs, office verification, generated documents, and operations messaging.

What was going on
Field Operations System
What I changed

What I did

  • ITP checklist execution and evidence capture
  • Field-to-office verification workflow
  • Generated PDF and email artefacts
  • Operations messaging and traceability
  • QA and release hardening for live workflows

Tools and software

DjangoPythonMobile and web workflowsPDF generationPostgreSQLDeployment hardening
More about this project

More detail

What was happening
Compliance work needed a traceable path from field checklist initiation to office review and final sign-off.
What I did
Unified checklist execution, evidence capture, document generation, and operations messaging into one auditable lifecycle.
What changed
Gives field crews and office coordinators a clearer way to complete, verify, and hand over compliance work.
What I can show
Repository-grounded delivery, QA, deployment, and document-flow evidence is available for a redacted public case study.
02

Case 02

SaaS Takeover
Live production takeover

Production Platform Takeover and Stabilisation

A live product taken over with focus on reliable releases, security, and ongoing delivery.

What was going on
SaaS Takeover
What I changed

What I did

  • Production implementation takeover
  • Deployment blocker fixes
  • Security and release hardening
  • Figma changes translated into production-safe code
  • Ongoing maintenance-phase delivery

Tools and software

ReactProduction deploymentSecurity hardeningFigma implementationRelease workflowsMaintenance delivery
More about this project

More detail

What was happening
A live platform needed a technical owner who could stabilise production delivery without stopping the next releases.
What I did
Took over implementation ownership, fixed deployment and security issues, and translated evolving design changes into production-safe work.
What changed
Keeps feature delivery moving while making the release path more reliable and accountable.
What I can show
The portfolio catalog records production takeover, deployment, security, Figma delivery, and maintenance-phase evidence.
03

Case 03

Confidential Engagement

Confidential Software Engagement

A confidential software engagement. Further project details cannot be shared under NDA.

What was going on
Confidential Engagement
What I changed

What I did

  • Confidential workflow implementation
  • Testing and review
  • Release preparation

Tools and software

Custom software
More about this project

More detail

What was happening
A client needed a tailored software solution. Further details are withheld under NDA.
What I did
Delivered a custom software workflow; implementation details are confidential.
What changed
The work addressed a client-specific need. Business outcomes are not disclosed.
What I can show
This engagement is covered by NDA. Client identity, product details, architecture, artifacts, and outcomes are withheld.
04

Case 04

AI & Automation
Internal application

RB Trends Internal Operations Platform

An internal tool that ranks Upwork jobs by suitability, matches each brief with relevant portfolio work, and helps prepare tailored proposals.

What was going on
AI & Automation
What I changed

What I did

  • Filter job listings by skills, budget, and suitability
  • Match job requirements with relevant portfolio evidence
  • Prepare structured, AI-assisted proposal drafts
  • Review ranked opportunities and hours estimates in generated reports

Tools and software

PythonDjangoOpenAIscikit-learn
More about this project

More detail

What was happening
Finding suitable work takes more than keyword search; each opportunity needs a fit check, relevant evidence, and a proposal tailored to its brief.
What I did
Combined job ingestion and filtering with AI-assisted analysis, portfolio matching, and proposal preparation in a repeatable Django workflow.
What changed
Gives proposal work a consistent path from opportunity review through evidence selection and drafting.
What I can show
A committed job-ranking and hours-estimator snapshot is available from 27 November 2025. It is archival evidence; no accuracy or revenue uplift is claimed.
05

Case 05

Research Automation

Freelancer Research & Rate Benchmarking

A market intelligence workflow that searches freelancer profiles, groups results by experience tier, and exports usable pricing research in JSON, CSV, and Markdown.

What was going on
Research Automation
What I changed

What I did

  • Preset and custom skill searches
  • Rate filters and experience banding
  • Top competitor summaries
  • Readable stakeholder-facing output
  • Retry logic around API limits

Tools and software

PythonMarketplace APIsCSV/JSON exportsMarkdown reportsFilteringStatistical summaries
More about this project

More detail

What was happening
Rate conversations and hiring decisions were happening without enough market context.
What I did
Turned raw search data into benchmark reports with tiered analysis and notable competitor extraction.
What changed
Useful for pricing, staffing, and positioning without having to hand-sort marketplace results.
What I can show
The repo documents presets, filters, export formats, and interpretation guidance for the resulting reports.
06

Case 06

Secure Integration

Microsoft Graph Local Connector

A local connector for Microsoft 365 data that syncs Teams chats and mail using delegated auth, encrypted token caching, and privacy-first defaults.

What was going on
Secure Integration
What I changed

What I did

  • Device code flow authentication
  • Encrypted token cache
  • Mail and Teams synchronization
  • Metadata-first exports
  • Tested client and auth modules

Tools and software

MSALMicrosoft GraphPythonCLI toolingJSON exportsTests
More about this project

More detail

What was happening
Needed secure Microsoft 365 access without a heavy hosted middleware layer.
What I did
Implemented local delegated auth, token protection, sync commands, and supporting tests and docs.
What changed
Makes Teams and mail data available to local tools while staying cautious about privacy and scope.
What I can show
The implementation summary documents auth flow, commands, tests, and security decisions in detail.
07

Case 07

AI & Automation
Workflow prototype

USS Site & Tech Brain

A case-based workflow for site observations, technical questions, and qualified review.

What was going on
AI & Automation
What I changed

What I did

  • Capture site observations against a case
  • Organise technical questions for review
  • Present evidence and OCR review signals
  • Show a path to qualified human review

Tools and software

Static HTML prototypePython source pack
More about this project

More detail

What was happening
Site observations and technical questions need a case-based way to gather context and guide qualified review.
What I did
Prototype an evidence-led flow around site observations, technical questions, and human review.
What changed
Makes the intended review workflow concrete without suggesting that automated signals replace technical approval.
What I can show
This is a static workflow prototype. Assistant and OCR results are synthetic; it does not run OCR, retrieve sources, or approve installations.

Ways I can help

How I usually add value

Maybe you know what needs building. If not, I can help work it out. I also take over existing apps.

Project type

New product or feature

Start with the idea or feature. Work out what it needs to do, then build a first version.

Project type

Taking over an existing app

I look at the code and release process, then fix what is blocking the next change. A rewrite is not the default.

Project type

AI and system connections

Connect the software and data you already use. Add AI when it helps, and check what happens when it gets things wrong.

Project type

Work out what to build

If you do not know what should be built yet, I can help work it out before you spend on a larger build.

If you are not sure what to build

Start by working out the problem

If you are still working out what to build, I can spend a week or two looking at the problem, trying the risky parts, and writing down what I would do next. If your scope is clear, we can talk about building it.

What I will send back

  • The problem and what should change
  • Who will use it and what they need to do
  • The software and data involved
  • Questions and risky parts to check
  • A next step and written estimate

You keep the notes either way. There is no requirement to hire me for the build.

Paid and fixed price, usually 1-2 weeks from A$2,000. I agree the work, price, and dates with you before starting.

Common Questions

What projects do you take on?▼

New product ideas, existing apps that need work, and business software that no longer fits. You do not need to have every detail worked out before we talk.

Can you take over an existing codebase?▼

How are estimates and billing handled?▼

How do you approach AI reliability?▼

What happens after launch?▼

Still have questions?

Send the rough idea, the app that needs attention, or the work your current software cannot handle. No finished brief needed.

What are you trying to build or fix?

A rough note is fine. Tell me what you want to do, what exists now, and what is getting in the way. I can ask if I need more detail.

Brisbane, Australia. Rough briefs are welcome. Prefer email?regan@rbtrends.com.au

Tell me what is going on

A few lines is enough. What should change, what do you have now, and where are you stuck?

No finished spec needed. Tell me what you want to build, what exists now, and what is getting in the way.

What helps me understand it

1. What should be different

What should the software let someone do that they cannot do now?

2. What you have now

An idea, an app, a process, or a set of tools that are already in use.

3. What is getting in the way

The part that is slow, broken, hard to change, or still unclear.

4. Anything you have tried

What has helped, what has not, and what you think might work next.

A rough starting point is enough

  • What you want to change
  • What you know and what you are still working out
  • The app, tools, or code already involved
  • What you would like to happen next

Send me the rough version.

You do not have to work out the whole plan first. That can be part of the job.

RB Trends

I build software, add AI when it helps, and take over apps that need work.

New products and AI featuresExisting appsBusiness softwareAPIs and data connections

Focus Areas

  • Client operations tooling
  • Marketplace and recruiting workflows
  • Microsoft 365 and API integrations
  • Internal dashboards and exports
  • AI-assisted review and summary tools

Contact

  • Tell me what you are working on
  • Async-first collaboration
  • Remote-friendly delivery
  • Regan handles the technical work
© 2026 RB Trends. Built around selected work, writing, and client readiness.