Graview Cloud for hiring

Four interviews done. Two write-ups missing.

Two roles, a dozen candidates, and three interviewers per loop. Keep candidates, stages, interviews and feedback in one app every interviewer can open. An interview with no write-up after two days is flagged, and so is one with nobody running it.

For hiring managers and the small team interviewing with them, before there's a recruiter or an ATS.

1 template
2 rules that watch
Private alpha · invite-only

Request an invite See the templates

Graviewacme.graview.app/a/engineering-hiring

Live

You, in Claude

Set up a hiring loop for two engineering roles: the candidates, the interview stages, and everyone's feedback.

graview · create_app4 kinds · 12 records · 2 rules

Candidates4

Ada Okaforonsite
Sam Reyesphone screen
Lin Parkoffer
Tom Ruizapplied

Interviews3

Ada · technicalTue · no feedbackTue · feedback in
Ada · system designWed · Marc
Sam · phone screenThu · Jen

Interviewers3

Priya2 interviews
Marc1 interview
Jen1 interview

Feedback2

Lin · hirePriya
Lin · strong hireMarc

RuleAda · technical was 3 days ago and nobody has written feedback

Rules2 of 2 hold

Youwrote the feedback for Ada · technicalnow
Marcmoved Lin Park to offer2 min
Claude, for youmade the app at acme.graview.app/a/engineering-hiring4 min

Sound familiar?

If you run hiring, you've said one of these.

“Four interviews done. Two write-ups missing. The debrief is in an hour.”
“Did anyone actually tell the candidate what's next?”
“I'm comparing notes from a doc, a Slack thread and someone's memory.”

For hiring

What the app holds.

Candidates by role and by stage
Interviews, and who still owes feedback
One view every interviewer shares

A week with it

What changes, day by day.

Monday
you describe the roles, the stages and the panel; each candidate gets a card with where they are.
After each interview
the interviewer writes feedback from their phone; a candidate with an interview and no write-up is flagged by name.
Debrief
every stage, every note, side by side; the decision and who tells the candidate, recorded.

Templates

Start from this one.

It's a complete app for hiring. Answer the questions it asks and it's yours to change. Or skip it and describe the job in your own words.

Template · 4 kinds · 2 rules

Hiring loop

Candidates, their interviews, and the feedback nobody has written yet.

Holds: Candidates Someone we're considering for the role.Interviews One conversation in a candidate's loop: a screen, a technical round, a chat with the team.Interviewers Someone on our side who interviews and writes feedback.Feedback What an interviewer thought after an interview, and whether they'd hire.
Rules it keeps: Every interview is written up within two daysEvery interview has somebody running it
It asks you: Which role are you hiring for?Who's already in the running? Names are enough.Who on your side will interview?

How it works

From a sentence to a shared app.

There is no setup. The app's shape comes from what you describe, and it changes when the job does.

Step 1
Describe it
Add Graview to ChatGPT or Claude once. Then say what you're organizing, in your own words. Or start from one of our templates on graview.cloud.
You: “Track our kitchen renovation and what's on order.”How to connect
Step 2
Get the app
About a minute later it's live at its own address on graview.app, with the records and rules the job needs. It shows up in your chat and opens on any phone.
okafor.graview.app/a/kitchen-renovation
Step 3
Invite people
Give each person a role: owner, editor, viewer, or one your app defines. Everyone sees each change as it lands, with the name of whoever made it, your AI included.
Here now: Nick, Sam and Ana
Step 4
Change it by asking
Ask for a deposit field or a budget warning and the app changes shape. Every record comes through. If one wouldn't, you're asked first, and earlier versions can be restored.
You: “Add a deposit field.” → version 2

Privacy

Your plans stay yours.

People put real money and real addresses into these apps. This is who can see them, and what happens when you leave.

Private until you share it

Only you can open a new app. Each person you invite gets a role: owner, editor or viewer.

Your AI has your permissions

A connected chat can do what you could do in that app, and nothing more. Its changes are labeled as its own, and it can never change who has access.

Sights decide who sees what

An app can keep some records to some people. A record you can't see is absent everywhere: on the page, in search, and in your chat.

One app can't reach another

Each app runs on its own, with its own storage, at its own address.

Not read, not used for training

We don't read your apps or train AI models on them. Staff can look only if you grant support access: read-only, for 24 hours, ended whenever you like.

Leave with everything

Export a whole app with its history at any time. Delete it and it's gone within 7 days, and from backups within 30.

Questions

What people doing hiring ask.

Is it an applicant tracking system?

It's the loop for a few roles at a time: candidates, stages, feedback, decisions. When you need job boards and offer letters, you'll want an ATS; export and go.

Who can see the feedback?

The panel for that role. Candidates never do; a note is never sent anywhere.

Other jobs

People keep track of all sorts.

Private alpha

Bring the candidates. Close the loop.

Graview Cloud is invite-only while we build it with its first people. Tell us what you'd make and we'll send an invite when there's room.

For you

Coming soon

Your own apps, kept as long as you like and exportable at any time. Free while the alpha runs.

For the people you invite