Capture · Propose · Deliver · Close
Qualify each bid, write the proposal from what your company knows, and run the win as a project with nothing re-filed.
01The workbench
Each member works inside the app it was added to and answers with citations. Before anything goes out, it waits for a person.
Scout Intake analystAnswered from the notice's files · 3 citations illustrative
Quill Proposal writerAsked all its questions at once · waiting on you illustrative
Cipher Compliance reviewerChecked against your review procedure · a person decides illustrative02One bid, the whole way
01 Pursuit · intake
Notices arrive from SAM.gov on each saved search's schedule, or you add them by hand, and they wait in one review queue. Approving one files the opportunity and its project together, so nothing is half-filed.
Scout answered from the notice's files, with citations.
The capture lead approves it.
02 Pursuit · proposal
The pursuit room keeps the opportunity with its response settings, its lists and the proposal itself: an outline and a document for each section. The crew answers from your files with citations and asks before it acts. Your writers decide.
Quill asked all its questions in one interview.
The proposal manager answers and decides.
03 Projects
When the bid is won, the same project moves to Projects with its files, worklists, forms and agreements, and the team works it in its folders.
Atlas keeps a backlog the team can see.
The project lead runs the worklist.
04 Projects · archive
A finished project is archived, read-only and out of the active lists. What the team learned goes into the Library, where the next bid can cite it.
Echo keeps each run in its memory, with who asked.
The project lead archives the project.
03The apps
Each app does one job and is sold on its own. The apps you take share one sign-in and the same projects.
Find the opportunity, qualify it, write the proposal, and keep every relationship that led there.
Run the won bid as a project, talk where the work is, and look after the people doing it.
Keep what the company has done with its sources, and see how the business is doing.
04The crew
Each member follows the procedures you publish and answers from what you teach it. It remembers what you correct. Learning from the team is still being completed.
Pixelnotices the small things
Tracefollows every thread
Adadesigns with intent
Dashclears the path
A11ymakes room for everyoneCiphertrusts, then verifies
Tempokeeps the work on time
Northknows which way is trueEcholistens before answeringQuillmakes intent clear
Boltkeeps things moving
Lunadoes her best work after dark
Sprocketbuilds better tools
Emberfinds another wayAtlassees the whole picture
Piplearns by doingScoutgoes to look first
Zenmakes hard days calm
Vegamakes the numbers trustworthy
Jinxasks the awkward questionQuill drafted technical volume §3.24 sources · awaiting approvalCipher checked section 3 against the matrix1 gap · filedScout read RFP §L and §M42 requirements · filed for review05Where it runs
Run it on Jeeraph cloud or in your own cloud. Either way, nothing is sent without a person.
How security worksWhere it runs
Accounts belong to the server your people sign in to, with no separate Jeeraph account service in between.
Your people
Access is set at the collection and can only be narrowed below it. The server checks every request.
Budgeted AI
Every model call reserves its budget before it runs and stops at the limit you set. With no budget, nothing runs.
Sources
The crew cites the file or Page behind each answer. A figure the product cannot support is not shown.
Book thirty minutes with the people who build it, or ask Jeeraph and see the real screen as it answers.