Limited published evidence · Sales, legal operations and engineering
Draft RFP responses, extract contract data, fix bugs and update SDKs
Box internal experiments
Early internal experimentation reported by Box's CEO in January 2025. Detailed deployments, controls and production outcomes are not established.
A published third-party example, not a Nuvepro customer case or evidence of a partnership.
What the source reports
Aaron Levie describes Box building internal agents to respond to RFPs and extract critical contract data for downstream automation. He also reports testing external agents for engineering bug fixes and SDK updates driven by feature requests. The post explicitly characterizes this work as early experimentation. It supplies useful work categories, but does not establish the repositories, extraction schemas, specific agent products, test results, merged fixes or release outcomes.
Source accounts: @levie
Reported technology: Internal and external AI agents described by Aaron Levie; individual tools not specified. Scope and outcomes are source-reported.
What the enterprise environment would need
The following is a proposed project design for an enterprise doing similar work. Published details are marked; the remaining systems, data and scenarios would be agreed for your project.
- Systems and tools
- Source-described: RFP, contract and engineering agent experiments, with individual tools unspecified. Proposed: use a controlled document workspace and separate test repository for each workstream.
- Data and state
- Proposed: provide fictional RFP requirements, approved product evidence, linked contract/amendment records and a small SDK repository with a reproducible issue and feature request.
- People and handoffs
- Proposed: sales reviews commitments, legal/operations reviews extracted contract meaning, and engineering reviews diffs, tests and compatibility. The post does not establish these implemented controls.
- Rules and authority
- Proposed: separate drafting from external submission, contract interpretation from consequential action, and candidate code changes from merge/release authority.
- Normal and exception cases
- Proposed: test unsupported RFP commitments, conflicting amendments, an unreproduced bug and a feature that breaks an existing SDK client. These cases are our proposed extensions.
- Reset and replay
- Proposed: restore document versions and clean repository commits, then replay each task with the same approved evidence and held-out regression suite. No reset system is published in the post.
A proposed simulation
An illustrative practice design derived from this work, not an executed assessment.
Proposed: prepare one evidence-backed RFP draft and contract extract, then demonstrate a bounded SDK bug fix and feature change in a test repository.
Review gate: Proposed: sales/legal owners verify evidence and retained authority, while engineers reproduce the issue and accept regression and compatibility results for the candidate changes.
Challenge the result: Proposed: an agent produces a plausible SDK fix that breaks an existing client. Passing the new feature check alone must not qualify the change for release.
What needs checking
- Proposed: verify RFP claims and extracted contract fields against authoritative source passages; preserve uncertainty and missing evidence.
- Proposed: reproduce the bug before the fix, run meaningful regression and compatibility tests, and inspect the actual diff and resulting repository state.
- Proposed: test that no response is submitted, contract action executed or code released without its designated owner's approval.
Review environment fidelity, human capability and agent performance separately. The enterprise’s accountable owners decide acceptance of the shared workflow and any operating use.
Shape this around your enterprise
Bring a similar workflow and the people responsible for it. Together, define the records and systems to use, the result your team will build or configure, and how its owners will check it. Nuvepro scopes the simulation, environment and preparation. Agree any existing-agent evaluation, implementation assistance and production responsibilities separately.
Sources and limitations
Curation review: . This is the date this source example was reviewed, separate from source publication dates.
- The source is an early operator account, not proof of present-day deployment, verified outcomes or a named external customer. Only the directly read opening supplies these four work examples.
- Specific tools, input schemas, evaluation results and actual downstream effects are undisclosed; detailed environment and control choices above are proposed.
- The proposed environment, practice project and checks are designs for discussion, not executed Nuvepro work or evidence of production readiness.
- Early internal agents for RFPs, contract extraction and engineeringSource publication: 2025-01-17