You will get a SaaS code and database audit: schema, security, and scaling risks
Project details
Most SaaS problems that surface at scale were decided early — in the schema, in the permission model, or in a shortcut that made sense at the time.
This is a focused audit of your existing app. Send whatever you're comfortable with: a schema dump, your Prisma or Drizzle schema file, API specs, or read-only repo access. I can work from the data model alone.
What I look at:
• Data model: normalization, indexes, constraints, and relationships that will not hold up as you grow
• Query patterns: N+1s, missing pagination, and the queries that get slow first
• Security: auth, roles, tenant isolation, and where the API trusts the client
• Structure: where business logic lives and what will cost most to change
What you get: a written report with every finding ranked by severity, why it matters, and a specific recommendation. Judgment from someone who has shipped multi-tenant SaaS — HerpSync and MapProx are both mine, both live.
Scope: one repository or database, one primary stack, up to roughly 40 tables. Larger systems on a custom quote — message me first.
Delivered in 4 days. One round of follow-up questions included. This fee applies toward the project if we build together.
This is a focused audit of your existing app. Send whatever you're comfortable with: a schema dump, your Prisma or Drizzle schema file, API specs, or read-only repo access. I can work from the data model alone.
What I look at:
• Data model: normalization, indexes, constraints, and relationships that will not hold up as you grow
• Query patterns: N+1s, missing pagination, and the queries that get slow first
• Security: auth, roles, tenant isolation, and where the API trusts the client
• Structure: where business logic lives and what will cost most to change
What you get: a written report with every finding ranked by severity, why it matters, and a specific recommendation. Judgment from someone who has shipped multi-tenant SaaS — HerpSync and MapProx are both mine, both live.
Scope: one repository or database, one primary stack, up to roughly 40 tables. Larger systems on a custom quote — message me first.
Delivered in 4 days. One round of follow-up questions included. This fee applies toward the project if we build together.
Programming Languages
JavaScript, TypeScriptCoding Expertise
Performance Optimization, SecurityWhat's included $400
These options are included with the project scope.
$400
- Delivery Time 4 days
- Number of Revisions 1
Optional add-ons
You can add these on the next page.
Fast 2 Days Delivery
+$150
45-minute findings walkthrough call
(+ 1 Day)
+$150
Second repository or service reviewed
(+ 2 Days)
+$250Frequently asked questions
About David
Custom Software & AI Solutions Developer
Selma, United States - 6:04 pm local time
Two systems I designed and built end to end are live:
• HerpSync — a multi-tenant SaaS for reptile breeders, serving public tenant pages on both platform subdomains and customer-owned custom domains (soft launch).
• MapProx — a field-sales mapping, route-optimization, and visit-tracking platform, with a React web app and a native iOS/Android app sharing one backend (publicly available).
Typical engagements:
- Focused SaaS MVPs
- Multi-tenant platforms with organization-level isolation and role-based access
- Internal workflow dashboards and customer portals
- CRM, payment, and third-party API integration layers
Stack: Next.js, React, TypeScript, Node.js REST APIs, PostgreSQL (Prisma/Drizzle), Stripe, RBAC, webhook and queue-based integrations, Claude and OpenAI API integration, and React Native/Expo mobile delivery.
My background is design first — a graphic design degree and web work since 2004 — so what I build is usable, not just correct. I've run EVC Studios since 2007.
AI-accelerated engineering speeds the repeatable work: research, implementation, testing, analysis, and documentation. It's an execution multiplier, not the product. Every requirement, architecture decision, data boundary, security-sensitive choice, and production release passes through my review and stays my accountability.
How I work: most projects start with a paid discovery and architecture review — data model, tech stack, permission structure, integration surface, and a build estimate — so we scope from evidence instead of assumptions. If the architecture is right, the build is predictable.
Good fit if you can describe the one core workflow your system must support first. Not a fit for template sites or page-builder work.
Steps for completing your project
After purchasing the project, send requirements so David can start the project.
Delivery time starts when David receives requirements from you.
David works on your project following the steps below.
Revisions may occur after the delivery date.
Access and orientation
I read through whatever you sent - schema, specs, or repo - and map how the system fits together: entities, relationships, request flow, and where the important business logic actually lives.
Data model and query review
I check the schema for normalization problems, missing indexes and constraints, N+1 access patterns, and modeling choices that will fight you as your data grows.