Skip to content
Evan Cortez
Live Demo

Evan Cortez

Software Engineer.
Product Builder.

I build software that improves business operations. From internal automation platforms to production SaaS products, I enjoy turning complicated workflows into software that people actually want to use.

BidzBase — production SaaS
BidzBase jobs pipeline in production

Impact

Results that matter to the business.

Measurable improvements in workflow automation, performance, reliability, and collections—not a list of frameworks.

60%

Revenue-critical workflow automated

66%

Reduction in API requests

70%

Faster application loading

99.99%

Deployment uptime

Production SaaS

Live with real users

Current Focus

Building

BidzBase

A live multi-tenant SaaS for subcontractors—estimates, proposals, scheduling, time tracking, and payments in one workflow.

Live in Production
ProductionReal UsersRecruiter Demo AvailableActively Shipping

Featured Product

BidzBase

From initial idea to a production SaaS with real users in roughly one month. BidzBase is the centerpiece of this portfolio because it shows the full loop: problem, product, architecture, and ongoing shipping.

BidzBase jobs pipeline for Ironpeak Trade Co.
Job pipeline

The Problem

Small subcontractors and trade shops still stitch estimating, proposals, scheduling, and collections together across spreadsheets, texts, and disconnected tools. Work falls through the cracks. Payments slow down. Owners spend their evenings chasing paperwork instead of running the shop.

The Solution

BidzBase is a production SaaS that follows the real workflow: estimate → send proposal → customer accept/decline → invoice → get paid. Scheduling, time tracking, and analytics sit on top of the same job data so the business runs from one system of record.

Target Customers

Independent subcontractors and small trade shops that need professional proposals, clear job status, and faster collections—without enterprise software overhead.

Product Philosophy

Solve contractor workflows first. Keep the product focused on estimates, proposals, payments, scheduling, and accountability. No feature for its own sake—especially not AI bolted on without a clear operational job to do.

BidzBase job detail with bids and payments
Job detail
BidzBase crew schedule board
Crew scheduling

Architecture

Multi-tenant by organization. A Django API owns domain logic. React powers the operator experience. PostgreSQL, Redis, and S3 back the core. Stripe, SendGrid, and real-time channels connect the product to money, messaging, and live updates.

Technical Decisions

Django for durable domain modeling and permissions. Stripe Billing for self-serve plans and Stripe Connect for customer payments. Docker on AWS for predictable deploys. Branded PDF generation so proposals look as serious as the work they represent.

Lessons Learned

Shipping a usable core early beats polishing adjacent surfaces. Multi-tenant edge cases show up fast once real users arrive. Payments and permissions deserve more design time than almost anything else in the stack.

Roadmap

Deepen the operations layer for growing crews, tighten analytics around cash and throughput, and keep expanding the parts of the workflow that still live in inboxes and spreadsheets.

What the platform covers

Multi-tenant SaaS architectureStripe subscriptionsStripe Connect paymentsSchedulingTime trackingAnalytics dashboardRole-based permissionsEmail automationDocker deploymentAWS infrastructurePDF generationReal-time updates
BidzBase analytics dashboard
Analytics
BidzBase customers list
Customers

Live Demo

Experience BidzBase

Explore the production demo without creating an account. Click through sample jobs, proposals, scheduling, and analytics in a live product environment—not a mockup.

Opens bidzbase.com/login?demo=1

Product Thinking

How I work.

Clear principles for turning messy operational problems into software people rely on.

Understand the workflow before writing code

I learn how work actually happens—handoffs, exceptions, and bottlenecks—before proposing software.

Technology should support business goals

Stack choices follow the outcome. Reliability, cost, and speed to value matter more than novelty.

Prefer simple systems over unnecessary complexity

Clear boundaries and boring defaults beat clever abstractions that nobody wants to maintain.

Ship early and improve through feedback

A usable product in users' hands beats a perfect plan. Iteration is the product process.

Measure outcomes instead of output

Fewer requests, faster load times, less manual work, and healthier cash flow—not story points.

Build products that solve real problems

If it does not reduce friction in a real workflow, it does not belong in the roadmap.

Design software around users—not developers

Interfaces and data models should match how operators think about their day.

Experience

Business outcomes first.

Selected accomplishments from shipping internal platforms and production systems at Right Angle Engineering—and building BidzBase.

Automated a revenue-critical workflow

Automated approximately 60% of a revenue-critical workflow, allowing the business to support significantly larger clients.

Reduced operational overhead so the team could scale without proportional headcount.

Cut API traffic at the architecture layer

Reduced API traffic by approximately 66% through architectural improvements.

Fewer calls, less load, and a clearer contract between frontend and backend services.

Made applications feel instant

Reduced application loading times by roughly 70%.

Users spend more time working and less time waiting on screens.

Hardened deployment infrastructure

Introduced Docker and AWS CDK infrastructure to support rolling deployments and approximately 99.99% uptime.

Shipping became routine instead of risky.

Brought visibility to operations

Designed internal analytics systems and introduced new operational metrics that improved quality assurance.

Teams could spot issues earlier and act with clearer signal.

Raised quality control standards

Built a configurable checklist platform that significantly improved quality control.

Consistent checks, less guesswork, better handoffs between stages.

Accelerated collections

Implemented automated payment workflows that accelerated collections and eliminated large amounts of overdue receivables.

Cash moved faster because follow-up stopped depending on memory.

Technologies

Tools used to ship.

Categories that backed BidzBase and production systems—not a skill meter.

Frontend

  • React
  • TypeScript
  • Next.js
  • CSS

Backend

  • Python
  • Django
  • Django REST Framework
  • Node.js

Cloud

  • AWS
  • S3
  • Lightsail

Infrastructure

  • Docker
  • AWS CDK
  • Nginx

Databases

  • PostgreSQL
  • MySQL
  • Redis

DevOps

  • GitHub Actions
  • Docker Compose
  • CI/CD

Payments

  • Stripe Billing
  • Stripe Connect

Architecture

A simple system with clear seams.

Hover each layer to see why it was chosen. The diagram mirrors how BidzBase is wired in production.

Connected integrations

Why this layer

Users

Operators, managers, and customers interacting with the product every day.

Education

Background.

Concise on purpose. The work above carries more weight than coursework.

Mountainland Technical College

Web Development

Completed 2024

Utah Valley University

Information Systems

Currently pursuing coursework

Contact

Let's talk about the work.

Open to conversations about product engineering roles where ownership, shipping, and business impact matter.

Command palette

Jump to a section or open a resource