Value now
Find the job. Apply on their behalf.
Once the worker says “I want to apply,” ACE makes sure the opportunity actually moves.
ACE · 2C Alpha Evidence · September 2026
Don’t go silent
after the résumé.
ACE turns one conversation into action toward the job a worker wants now, grows career data they own, and stays with them through application, interview, offer, and day one.
Asset that grows
Career data that becomes a résumé
Experience, preferences, priorities, and progress stay visible and editable by the worker.
Long-term value
A personal career agent on their side
ACE helps explain experience and keeps looking for better work over time.
The answer to Dave
We are not building another job board or résumé tool.
01
Why build it
Workers who spoke with us are abandoned after a résumé or phone screen.
02
Who it serves
Mobile-first workers who struggle to update résumés or apply across employers on their own.
03
What Alpha completes
One connected experience across conversation, profile, match, application, interview, offer, and first day.
04
What success feels like
The worker behaves as if: “If I tell ACE, my job search keeps moving.”
The Alpha boundary is not résumé creation. It ends when we can confirm that the worker made it to day one.
Two AIs · One name would blur the duty
HOPE represents the employer. ACE represents the worker.
HOPE
Employer-side AI recruiter
Understands the job, sources and screens candidates, and advances the employer’s hiring decision.
Same labor market
Different duty
Different duty
ACE
Worker-side personal career agent
Holds the person’s preferences and career data, searches across employers, applies with permission, and stays through the first day.
If both share the same name, a worker cannot tell whether the AI works for the company or for them. The naming boundary is a trust boundary.
Two entry routes · One ACE
Different entry points. The same need: an agent that keeps the next job moving.
Route A · Google ad
Actively searches and clicks an ad
- Arrives with clear intent to find better work
- Primarily uses a phone, rarely a computer
- May not speak English as a first language
- Shares experience in conversation to build a résumé
Route B · Indeed application
Arrives through one specific job
- Has already applied to a particular role
- HOPE runs the prescreen
- If it is not a fit, HOPE asks about other jobs
- That permission and preference state transfers to ACE
ACE should not create a new person for every entry route. One worker identity should connect multiple applications and conversations.
Today · An eight-step automation map
Résumés and AI screens work. ACE does not yet connect what happens around them.
Partial01 · Entry
Google ad and Indeed entry points exist, but they do not form one continuing worker relationship.
Automated02 · Experience + résumé
Voice intake captures experience and generates a profile or résumé.
Partial03 · Preferences
Captured at intake, but workers cannot review, update, or rank priorities.
Not built04 · Verify, correct + upload
No way to fix facts or upload ID, work-authorization, license, and credential documents.
Not built05 · Next-job search
No ongoing loop finds and recommends alternative jobs.
Partial06 · Apply
Specific-job submission works; worker-facing proof and status do not.
Automated07 · AI screen
AI phone screens and some SMS scheduling and reminders run today.
Manual / disconnected08 · Employer interview → day one
Employer interview, outcome, offer, and first-day continuity rely on people.
AutomatedPartialNot builtManual / disconnected
Four handoffs where automation stops
Individual steps run. The worker's promise does not pass to the next action.
01 · Conversation + documents → correct record
No correction or document upload
Workers cannot fix misheard facts or upload identity, work-authorization, license, and credential evidence.
Today: human edits; no upload path02 · Preference → next job
Consent triggers no search
Permission and preferences for other roles are captured, but ongoing search never begins.
Today: not built03 · Intent → proof
“Please apply” can stall
Specific-job submission exists, but worker-visible completion and status do not connect.
Today: manual SMS bridge04 · Employer interview → day one
No single next-action owner
Employer replies, interview times, outcomes, offers, and first-day details are not managed together.
Today: human-ledCommon gap: persistent ACE state for the worker’s latest facts, intent, and next action across jobs and channels.
Map of four patterns · A → B → C → D
A and B are entry routes. C and D are breaks that follow.
Entry · How workers arrive
A 08–10
Google ad
Actively searches for work and clicks an ad. A résumé gets made; sustained matching and hiring remain unproven.
B 11–13
Indeed application
A specific-job applicant gives permission and preferences for other roles.
Break · Where the relationship fails
C 14–16
Facts cannot be confirmed
Workers cannot correct misheard facts or submit identity and credential documents.
D 17–19
Action stalls
Application intent or employer-interview interest does not produce a timely next step.
These are not four tracked people. The evidence combines Google ad route observations, production Indeed/MES records, and recurring operations-observed errors.
Case A · Google ad · Activation success
For someone without career data, we can return the first usable version of their story.
Entry
Actively searches for work, clicks a Google ad, and arrives ready to change jobs.
Reality
No computer, limited English, and a résumé that is outdated or does not exist.
What ACE does
Accepts a résumé upload or structures experience and preferences from a short conversation.
Where we reach today
Résumé creation and a response of “I want this job.”
Real users in Texas, New York, and elsewhere include Spanish-only and primarily French-speaking immigrant workers. The value is not completing a form well—it is making experience legible through conversation.
Case A · Evidence boundary
We proved the first value. We have not yet proved the value all the way to a job.
Evidence we have
- A conversation can become a finished résumé
- Workers respond that they are interested in suggested jobs
- A phone and conversation are enough to get started
- Someone without career data can still enter
Evidence we do not have yet
- Other jobs can be found continuously
- Interest becomes a completed application
- Employer replies are reliably captured
- The relationship survives through interview, offer, and day one
We do not claim hiring success on this route. Alpha must prove that silence after the résumé can become the first confirmed start.
Source: current Google ad route + field observation
Case A · Product implication
A completed résumé should be the beginning of the ACE relationship.
01 · Talk
Share experience and current preferences in conversation.
02 · Confirm
Verify contact facts and provide needed documents.
03 · Profile
Receive an editable career profile and résumé.
04 · Match
See fitting jobs with a short reason for each.
05 · Decide
Say “apply” or “not this one.”
06 · Apply
ACE submits and records proof and status.
07 · Follow
If nothing moves, ACE follows up or finds the next match.
08 · Interview
Coordinate the interview and keep one confirmed schedule.
09 · Offer
Organize terms and help the worker decide.
10 · Start
Carry onboarding and attendance through day one.
Case B · Indeed · Rich intent, no action
Even when one job is wrong, the conversation already contains enough to find the next one.
Entry
Applies through Indeed to a specific MES Engineer role.
Already captured
Experience, desired pay, location, shift, credentials, language, and start date.
Also captured
Why they want to move, what they want to change, and permission to suggest other roles.
Result today
The data is stored, but no other-job search or recommendation happens.
The prescreen learns more than whether the worker fits one job. It learns what could fit next. The missing piece is not another question—it is the next action.
Case B · Production evidence · Anonymized
MES Engineer conversations alone contain explicit permission and direction for other jobs.
Structured interest recordCandidate 1
“Open to alternative roles, especially manufacturing systems, SCADA, factory automation, and IT/OT integration.”
Structured interest recordCandidate 2
“Open to software engineering, manufacturing systems, automation, SRE and cloud platform engineering.”
Production snapshotMES Engineer
50
Unique candidates with structured interest in alternative roles
The records hold not just role interest, but growth goals, autonomy, work style, and communication preferences.
Missing product actionToday
- No search against other job inventory
- No reasoned recommendation back to the worker
- No worker-visible place to revise preferences
- No conversion from interest into application
Source: structured production candidate-interest data. Names, contact details, and company names removed. Count reflects the MES Engineer position at the time of research.
Case B · Product implication
“You may show me other work” is not an answer to store. It is the trigger for ACE to begin.
01
Create one source of truth
Merge answers from job-specific screens into one worker profile.
02
Ask for priorities
Learn what is non-negotiable across pay, growth, place, hours, and environment.
03
Recommend with reasons
Explain briefly why each job fits and where it differs.
04
Turn intent into action
On “I want to apply,” begin submission, additional questions, and tracking.
The information is not missing. Without ACE, information we already earned is not used to find the next job.
Case C · Voice intake · Wrong data
Workers cannot correct what we heard or submit documents that support their profile.
Input
The worker speaks their name, history, employers, and locations into a phone.
What goes wrong
Names and spellings are incorrectly structured from speech recognition.
Worker’s position
There is no place to fix facts or upload identity, work-authorization, driver’s license, or occupational credential files.
Downstream effect
The wrong résumé, application data, or contact route gets used.
The recurring errors are the worker’s name, a prior company, a prior work location, and email. A wrong email can prevent the employer’s next message from ever reaching the worker.
Source: operator-observed errors + current upload gap
Case C · Failure chain
The employer sees an unresponsive candidate. The worker does not even know a message was sent.
1 · Voice capture
Name, employer, location, and email come from conversation.
2 · Silent error
A proper noun or email is stored incorrectly.
3 · Employer sends
The employer writes to the address on file.
4 · False conclusion
Nothing arrives. The employer sees no reply; the worker sees no progress.
Data-quality failure
Trust in the résumé and profile falls.
Reachability failure
A qualified worker loses the employer connection.
Accountability failure
No one can see where the process stopped.
Case C · Product implication
ACE should act on facts the worker confirmed—not what the system thinks it heard.
Verify
Read critical fields back
Confirm name, email, phone, employer, and location one field at a time. Show email spelling and test reachability.
Upload
Receive supporting documents
Let workers upload identity, work-authorization, driver’s license, and occupational credential files. Link them to profile fields and distinguish pending review from confirmed facts.
Edit
Return the profile to the worker
Make the field-level career profile—not only a PDF résumé—the editable source of truth.
Recover
Detect unreachable states
When email bounces or a response is overdue, fall back to SMS. Never bet a critical message on one channel.
Connect conversation, worker edits, and submitted documents in one profile. Upload alone must not mark identity or qualifications as confirmed.
Case D · MES Engineer · Explicit intent
The candidate has already said exactly what they want us to do next.
State
The AI phone screen is complete and the employer wants the next interview.
Candidate intent
They reply that they want to proceed, want us to submit, and ask when the client interview is.
Process today
A person reads the SMS and, a day later, sends a link or offers to submit.
Break
Intent does not become immediate submission and visible progress.
The candidate is not undecided. ACE has not taken ownership of the intent and completed the next operational step.
Case D · Production SMS · Anonymized
“Move forward” and “Please submit” are execution commands—not comments awaiting another confirmation.
Candidate → BlucorAfter client interest
“Yes, I’m interested to move forward.”
Manual reply · following dayBlucor → Candidate
“Would you like to apply directly through the link we shared?”
Candidate → BlucorSame sequence
“So when I can get interview with client?”
“Please submit.”
Manual reply · following dayBlucor → Candidate
“We’ll submit it for you and let you know once it’s done.”
No durable worker-facing record then shows proof of submission, current state, or the next deadline.
Source: production SMS for the MES Engineer role. Names, company names, job links, and contact details removed. Grammar preserved verbatim.
Case D · Scheduling evidence · Anonymized
Automation is not management if it cannot answer the worker’s “What is actually happening?”
CandidateTimezone confusion
“Do I have interview at 10am MST again?”
Automated replyWrong intent classification
“Thanks for your feedback — we’re working to make the interview experience even better!”
CandidateDate confusion
“I have scheduled call on Monday, not today.”
System stateSame day
- The worker gave a weekday and date that conflicted
- The system confirmed the conflicting date as entered
- Reminders and a call proceeded that same day
- The worker had no source of truth for the confirmed schedule
Source: production SMS. The sequence shows the state management, intent understanding, and exception recovery required across Alpha—not only employer interviews.
Cross-case comparison
The break happens in different places. ACE must take the same kind of ownership.
| Dimension | A · Google ad 08–10 | B · Indeed 11–13 | C · Data/docs 14–16 | D · Stalled action 17–19 |
|---|---|---|---|---|
| Role in the story | Entry: active search, then ad click | Entry: job application | Break: facts and documents | Break: next action |
| What the worker did | Shared experience and expressed job interest | Consented to recommendations for other roles | Spoke identity and career facts | Asked us to proceed and submit |
| Asset created | Résumé and initial profile | Detailed preferences, reason to move, permission | Career data and contact details | Screen result and explicit intent |
| Where it breaks | Silence after the résumé | Preference triggers no search | Cannot fix facts or submit documents | Intent triggers no immediate action |
| ACE responsibility | Keep proposing the next job | Use preferences in matching | Receive documents and track review status | Own submission, schedule, and outcome |
| Evidence today | Interest only | Consent only | Error flows downstream | Human intervention |
Root cause
Today’s system processes conversations.
ACE holds a commitment to a person.
ACE holds a commitment to a person.
State
The current truth about this person
Verified identity, history, preferences, priorities, consent, applications, interviews, offers, and start date.
Judgment
What should happen next
Which job to suggest, what to verify, whether to wait or follow up, and when to escalate an exception.
Agency
Finish the action that was promised
Complete submission, extra answers, scheduling, reminders, outcomes, offer, and first-day confirmation across channels.
Silence is not the event “we did not send a notification.” It is the product state “no agent owns the next action.”
ACE compounds value in three layers
Every step toward today’s job makes the next job easier.
The job they want now
Find fitting work, apply after the worker says yes, and carry the process through interview, outcome, offer, and day one.
Living career data
Let the worker update history, preferences, contact details, applications, and employment. Keep review status for documents they submit. Generate the résumé from this data.
A personal career agent
Advise how to explain experience and keep searching for better conditions and growth. Stay with the worker across their career.
The near-term benefit advances the job. The record of that work becomes the long-term asset. That asset improves the next advice and match.
The smallest complete Alpha experience
It begins with conversation. It ends with “I made it to day one.”
01 · Join
Enter ACE from a Google ad or post-application SMS.
02 · Talk
Upload a résumé or have a short conversation.
03 · Verify
Confirm facts, upload needed ID, work-authorization, license, or credential files, and show review status.
04 · Prefer
Set conditions, priorities, and non-negotiables.
05 · Match
Recommend fitting work with reasons.
06 · Apply
Act on intent and record proof of submission.
07 · Complete
Finish additional questions and the AI screen.
08 · Interview
Coordinate the employer interview and manage the schedule.
09 · Offer
Organize outcome and terms; support the decision.
10 · First day
Confirm onboarding and attendance on the start date.
How to build Alpha
Reuse the working components. Connect the four broken handoffs.
Reuse · Working today
Existing execution components
- Voice intake for experience and preferences
- Résumé and structured-assessment generation
- Job data and specific-job matching foundation
- Submission to a specific job
- AI phone screening
- Some two-way SMS and scheduling
- Application-stage synchronization
Build · Connect in Alpha
The ACE continuity layer
- One worker identity and editable profile
- Secure upload and review status for ID, work-authorization, license, and credential files
- Verified contact routes and failure recovery
- A source of truth for preferences and priorities
- An agent loop for other-job recommendations
- State for submission proof, progress, and unanswered actions
- Unified employer-interview SMS, schedule, and outcome
- Ownership of every next action through first day
SMS scheduling for an AI phone screen is not the same as automated management from the employer interview through day one.
Autonomy boundary
ACE should move aggressively while career decisions remain with the worker.
Automate in Alpha
Low-risk continuity work
- Search and job recommendations
- Questions that verify facts
- Status, rejection, and next-match updates
- Scheduling within approved availability
- Reminders and no-response follow-up
The worker decides
Explicit intent in Alpha
- Whether to apply to a job
- Material changes to the profile
- Which documents to submit and with whom to share them
- Final interview-time confirmation
- Whether to accept or decline an offer
- Commitments on pay and start date
Human exception
High risk, conflict, or repeated failure
- Mismatch between worker facts and submitted documents
- Fraud or suspicious contact
- Legal, discrimination, or sensitive-data issues
- Materially conflicting terms
- Repeated communication or scheduling failure
Long term, ACE can auto-apply within pre-approved boundaries such as pay, distance, and role. Alpha begins with an explicit “I want to apply.”
Alpha pass condition
Move at least one real worker from profile to a confirmed first day—with no human ops on the normal path.
Critical-field corrections, required-document submission, and pending versus confirmed review status.
Time from profile completion to the next meaningful action. Time spent silent.
Reply rate to ACE, response to recommendations, and recovery after no response.
Intent-to-submit time, proof-of-submission rate, and failure recovery.
Employer-interview rate, schedule confirmation, reschedule, attendance, and no-show.
Offers received, terms confirmed, accept or decline, and reason.
Readiness before start, confirmed attendance, and reason for failed starts.
Human touches on the critical path. Target: zero on the normal path.
Repeatability: run the loop from both Google ad and Indeed, then prove the same state model works for the next worker.
The Alpha decision
From a company that creates résumés
to ACE, the agent that moves each worker forward.
1
Never abandon someone after the first conversation
ACE owns the next action, deadline, and unanswered item—and keeps communicating.
2
Return the worker’s data to the worker
Make résumé, preferences, and progress a career profile they can see and correct.
3
Own the outcome through day one
Manage recommendation, application, interview, offer, and onboarding as one state.
Tell ACE once. The right work keeps moving.
HOPE advances hiring for the employer. ACE advances the worker’s career. Connected, they let Blucor execute all the way through the hiring journey—for both sides.