Regan Behrendorff / Brisbane-based independent developer

I help service businesses and SaaS teams fix fragile workflowswith reliable internal tools and automation.

When spreadsheets, inboxes, APIs, and reporting start creating delays or duplicated work, I map the real process, build the smallest useful system, and leave the review and handover path visible.

Workflow AutomationAI-Assisted TriageOperational ReportingCustom Service Portals

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

Operating approach

The first step is usually a focused workflow diagnostic: clarify the bottleneck, identify the safest leverage point, and define what a useful first release needs to prove.

01

Standardise the manual workflow before writing automation logic

02

Keep operator review checkpoints embedded directly inside the pipeline

03

Deploy high-value components immediately to measure operational impact

Eliminate Manual Handoffs

Move information between people and systems without repeated copying and manual follow-up.

Connect Fragmented Systems

Keep inboxes, spreadsheets, APIs, and databases working from the same information.

Reduce Admin Overhead

Automate routine admin while keeping exceptions visible to the person responsible.

Delivery proof

One accountable owner from workflow map to handover.

The useful outcome is not a decorative demo. It is a system that solves a real problem, handles exceptions, and can be operated.

Delivery loop

From ambiguity to ownership
01

Map

Find the handoff

02

Build

Prove one path

03

Handover

Leave it operable

Every release should make the owner, exception path, and next decision easier to see.

01

Map the manual task and the person who owns it

02

Ship the smallest useful workflow end to end

03

Make review, failure handling, and handover explicit

$200k+
Upwork earnings
100%
Job Success Score

First step

Workflow diagnostic

Before building anything, I review how the workflow currently operates, where time or information is being lost, and which part is worth fixing first.

You receive

  • A map of the current workflow
  • The main bottlenecks and failure points
  • A recommended first working release
  • The systems and integrations involved
  • A written estimate with an agreed cost cap

The diagnostic is scoped before it begins. You can use the resulting plan whether or not I complete the build. It does not commit you to a build.

Paid and fixed-scope, usually 1-2 weeks, from A$2,000. Cost and timing are confirmed in writing before work starts.

Where the work usually starts

Most projects start with one workflow that is costing the team time, visibility, or confidence. The first job is to make that problem clear.

01

AI-enabled internal tools

Useful operator-facing software that turns repetitive work into a clearer, reviewable workflow.

  • ▸A working automated workflow
  • ▸An internal dashboard or operational interface
  • ▸Review and approval controls for AI-generated work
02

Connected operational systems

Integrations that connect inboxes, spreadsheets, APIs, databases, and business rules.

  • ▸Connected APIs, spreadsheets, inboxes, and databases
  • ▸A data extraction or reporting pipeline
  • ▸Monitoring, validation, and failure handling
03

Takeover and stabilisation

A calm technical owner for an existing codebase, rough product, or unreliable release path.

  • ▸A clear path for the next release
  • ▸Documentation and practical handover notes
  • ▸Focused fixes before larger feature expansion

What you can expect to leave with

A working automated workflowAn internal dashboard or operational interfaceConnected APIs, spreadsheets, inboxes, and databasesA data extraction or reporting pipelineReview and approval controls for AI-generated workMonitoring, validation, and failure handlingDocumentation and practical handover notesA clear path for the next release

Selected work

Work shown through the problem it solved

Each project starts with the operating problem, then shows what changed, what was delivered, and where the evidence ends.

Workflow systemsResearch automationSecure local integrationsOperator-first tooling
01

Case 01

Field Operations System

Construction Compliance Platform

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

Problem-led delivery
Field Operations System
Built for one real operating constraint

What changed

  • 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

Technical detail

DjangoPythonMobile and web workflowsPDF generationPostgreSQLDeployment hardening
Read the case file

Case file

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

Case 02

SaaS Takeover

Production Platform Takeover and Stabilisation

A live production platform takeover focused on deployment reliability, security fixes, Figma-led implementation, and ongoing release ownership.

Problem-led delivery
SaaS Takeover
Built for one real operating constraint

What changed

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

Technical detail

ReactProduction deploymentSecurity hardeningFigma implementationRelease workflowsMaintenance delivery
Read the case file

Case file

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

Case 03

Document Intelligence

Governed AI Contract Assistant

A document and compliance intelligence workflow combining PDF ingestion, structured retrieval, context-controlled conversation, and governed responses.

Problem-led delivery
Document Intelligence
Built for one real operating constraint

What changed

  • Document and PDF ingestion
  • Structured extraction quality controls
  • Context-grounded retrieval
  • Governed response behaviour
  • Acceptance and release-readiness evidence

Technical detail

PythonRAGDocument processingStructured validationRetrieval workflowsSafe response behaviour
Read the case file

Case file

problem
Contract and compliance work needed faster document handling without hiding uncertainty or weakening traceability.
approach
Built a governed retrieval and conversation workflow with document processing, context control, validation, and safe response behaviour.
value
Makes document intelligence more reviewable and useful in high-stakes workflows without claiming legal or accuracy guarantees.
proof
Redacted architecture and implementation evidence supports the public case study; legal outcomes and accuracy guarantees are excluded.
04

Case 04

Workflow System

RB Trends Internal Operations Platform

A Python-first operations layer for opportunity intake, applicant review, communication triage, reporting, and market intelligence.

Problem-led delivery
Workflow System
Built for one real operating constraint

What changed

  • Job feed search with suitability scoring
  • Proposal and applicant export workflows
  • Weekly spend and hour reporting
  • Inbox summaries and follow-up support
  • CLI and GUI paths for different operator needs

Technical detail

PythonUpwork GraphQLREST APIsOpenAIPyQt6Markdown reporting
Read the case file

Case file

problem
Too many disconnected tasks across job intake, hiring, messaging, and reporting.
approach
Built thin wrappers around stable API surfaces, then layered exports and operator tools on top.
value
Gives a small team repeatable process instead of relying on memory and manual checks.
proof
Used across RB Trends' opportunity intake, contractor oversight, communication review, and weekly reporting, with repeatable exports, tested integrations, and documented recovery paths.
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.

Problem-led delivery
Research Automation
Built for one real operating constraint

What changed

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

Technical detail

PythonMarketplace APIsCSV/JSON exportsMarkdown reportsFilteringStatistical summaries
Read the case file

Case file

problem
Rate conversations and hiring decisions were happening without enough market context.
approach
Turned raw search data into benchmark reports with tiered analysis and notable competitor extraction.
value
Useful for pricing, staffing, and positioning without having to hand-sort marketplace results.
proof
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.

Problem-led delivery
Secure Integration
Built for one real operating constraint

What changed

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

Technical detail

MSALMicrosoft GraphPythonCLI toolingJSON exportsTests
Read the case file

Case file

problem
Needed secure Microsoft 365 access without a heavy hosted middleware layer.
approach
Implemented local delegated auth, token protection, sync commands, and supporting tests and docs.
value
Makes Teams and mail data available to local tools while staying cautious about privacy and scope.
proof
The implementation summary documents auth flow, commands, tests, and security decisions in detail.

Engagement patterns

How I usually add value

The engagement usually starts by clarifying the workflow, choosing the smallest useful release, or taking ownership of an existing system that has become difficult to operate.

Engagement pattern

New product or major feature build

Build a focused product surface or major feature with clear architecture and an end-to-end first release.

Engagement pattern

Existing platform takeover

Take ownership of an existing codebase, find the real bottlenecks, and stabilise delivery without starting over.

Engagement pattern

AI, automation, and data integration

Connect the systems already in the workflow and add AI where it improves the task without hiding failure modes.

Engagement pattern

Technical audit and delivery plan

Turn a rough product, workflow, or release problem into a prioritised technical plan before more build work begins.

Common Questions

What kinds of projects are the best fit?▼

The best fit is usually an internal tool, workflow automation project, reporting system, or narrow product surface where there is real operational friction and a clear owner. I work best when the problem is real enough to describe and one person can stay accountable for the technical path.

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 workflow, the point where it breaks, and the result you want to improve. I can then suggest whether a diagnostic, a focused build, or a takeover conversation is the right next step.

Start with a workflow diagnostic

Start with the workflow that is costing you time

You do not need a finished specification. Describe the process, the point where it breaks, and what a better result would change.

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

Start with a workflow diagnostic

Share the workflow, the bottleneck, and the result you want. I will review the context and suggest the clearest next step.

Useful first notes include the current process, the tools involved, the constraint that matters most, and what a successful result would change. No finished brief is required.

Useful context to include

1. Current workflow

What people do today, in order, from the first step to the final handoff.

2. Where it breaks

The slow step, repeated admin, missing visibility, or handoff that causes the most friction.

3. Systems involved

The apps, inboxes, spreadsheets, databases, or APIs already in the loop.

4. Desired outcome

What should become faster, clearer, easier to review, or easier to maintain after the work is done.

Good first projects usually have

  • A repeated task with a clear owner
  • A bottleneck that affects delivery, reporting, or accuracy
  • Existing systems that need to work together better
  • A narrow first version that can ship quickly

If the problem is clear enough to describe, it is clear enough to discuss.

Send the rough version. Specific detail beats polished language, especially when the workflow is still messy.

R
RB Trends

Portfolio site for practical engineering work across AI-assisted workflows, internal tools, reporting systems, and connected operations software.

Python automationReact + Next.jsAI workflow designReporting systems

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

  • Use the workflow diagnostic form to start the next step
  • Async-first collaboration
  • Remote-friendly delivery
  • Founder and operator delivery operations
© 2026 RB Trends. Built around selected work, writing, and client readiness.
WorkPrivacy PolicyTerms of ServiceCookie and privacy details