01 / Extraction
Structure first, then edit.
AI document extraction turns the resume into typed sections the owner can review and correct before anything is published.
Case study 05 · Serverless product delivery
Turn a resume into a web presence.
ResFol.io takes a PDF or DOCX resume and produces structured content, an editable profile, and a hosted professional site, with account, checkout, analytics, and recruiter-facing experiences on the same serverless rails as Contractor CRM.
- Role
- Product architect, full-stack and cloud builder
- Users
- Individual professionals and job-seekers
- Stack
- AWS Lambda, API Gateway, DynamoDB, S3, Cognito, Bedrock, OpenSearch, Stripe
- Boundary
- Publicly accessible product; roadmap and unit-economics claims are not made here
The problem
A resume is a document. A professional presence is a product.
Most people have a resume and no website, because a website means hosting, design, and upkeep they will not do. The product has to take the document they already have and carry it the rest of the way without asking them to understand any of that.
That is an extraction and provisioning problem more than a design problem: parse an unstructured document into structured content, let the owner correct it, generate a site, provision hosting, take payment, and keep all of it consistent with one customer identity.
What I built
Document in, hosted site out.
The same serverless discipline as Contractor CRM, applied to a different user and a different job.
02 / Provisioning
Checkout provisions the site.
Billing state, not a manual step, triggers hosting, so the customer never waits on a person.
03 / Tenancy
One identity, many surfaces.
Account, profile, generated site, analytics, and recruiter views share one customer boundary and one set of keys.
Architecture
From upload to hosted profile.
Scale-to-zero services keep the operating shape small while preserving explicit boundaries between identity, workflow, data, and delivery.
- 01 / Event
Upload, edit, or checkout
Account creation, resume upload, profile edit, or payment event.
- 02 / API
Workflow entry
API Gateway and Lambda validate identity, tenant, request, and product state.
- 03 / Data
Durable customer state
DynamoDB records, S3 documents and assets, Cognito identity, search index.
- 04 / Automation
Extraction and provisioning
Document extraction, structured generation, semantic search, billing, and hosting actions.
- 05 / Experience
Hosted result
Editable profile, generated public site, analytics, and recruiter-facing views.
The product
Upload a resume and watch it become a site.
Live
ResFol.io is publicly accessible: resume upload, AI document extraction, an editable profile, checkout-triggered provisioning, analytics, and recruiter-facing views, on multi-tenant serverless AWS. The product is the artifact; nothing here is a mockup.
Open ResFol.io ↗Outcome
A public product, not a demo.
ResFol.io is publicly accessible. The running product is the evidence for this case study: create an account, upload a resume, and watch the site appear.
What it proves is integration rather than any single feature: identity, document extraction, payment, generated content, hosting, and ongoing use meeting in one flow that a customer can complete alone.