All applications583

Find your application

583 applications

Open full catalog

Browse applications by category or open the full catalog.

Publishing House ERP · Available now

Publishing house ERP from manuscript to print run.

Publishing House ERP connects editorial work with the production record for a title. A publishing project holds its owner, dates, budget and status.

  • No per-user fees
  • Manual work is free
  • Configure it in Proto
OverviewProject Pipeline
Publishing House ERP · Projects

Project Pipeline

Projects in one list

New project
Projects in view
6
Total budget
3,290
Planned
2
Approved
2
Planned2
The Orchard at Low Tide, first editionPRJ-75277
870
15 Nov
Where Cedar Meets Rain, fall listPRJ-80796
250
24 Nov
Add
Approved2
A Map of Quiet Rivers, spring releasePRJ-83573
20
19 Nov
The Last Winter Orchard, audio editionPRJ-82430
770
29 Nov
Add
In production1
After the Lanterns Fade, paperbackPRJ-87993
690
12 Nov
Add
Review1
The Glasshouse Letters, illustrated editionPRJ-15156
690
17 Nov
Add
The Orchard at Low Tide, first editionProjects · PRJ-75277
Planned
OwnerLeila Mercer
Starts at15 Nov
Due date19 Nov
Budget870
Approve content versionPRJ-75277 · The Orchard at Low Tide, first edition

Rights Reviewer checks current rights coverage and approves the selected file version.

Waiting for Rights Reviewer
ApproveReturn
Example screen with sample data
Tables, ready to use
11
Saved views
14
Roles with set permissions
6
Reports and dashboards
8
Features

Follow each title's work

Every feature works on the same records. Pick one to see the screen your team works in.

Publishing projects

Give each title an owner, production dates, budget and a visible status.

  • Project owner
  • Budget baseline
  • Work boundary
  • Projects
  • Content items
  • Production tasks
  • Project costs
  • People
Explore publishing projects
OverviewContent Approval Inbox
Publishing House ERP · Publishing projects

Content Approval Inbox

Approval conditions

New
TitleStatusOwnerProjectDue at
The Orchard at Low Tide, chapter proofsReviewJonah OkaforThe Orchard at Low Tide, first edition25 Nov
Author interview for spring catalogReviewMalik ChenThe Orchard at Low Tide, first edition23 Nov
Back cover copy for Cedar Meets RainReviewTariq BanerjiThe Glasshouse Letters, illustrated edition22 Nov
Glasshouse illustration captionsReviewMalik ChenWhere Cedar Meets Rain, fall list05 Nov
Blue Water reading guideReviewPriya HaddadNotes from a Borrowed City, revised edition11 Nov
6 of 6 records
The Orchard at Low Tide, chapter proofsContent items · CI-92605
Review
OwnerJonah Okafor
ProjectThe Orchard at Low Tide, first edition
Due at25 Nov
Example screen with sample data
Process

From submission to production

From manuscript to approved content ships ready to use. One step needs a named approval before the work moves on: Approve content version (Rights Reviewer).

Drag a card to another stage, or focus it and use the arrow keys. It updates to match the stage.

  1. Open project

    Name the owner, dates and budget for the title.

    The Orchard at Low Tide, first editionPRJ-75277 · Publishing Director
    Open projectBy Publishing Director
  2. Receive manuscript

    Record the submission and assigned editor.

    The Orchard at Low Tide, first editionPRJ-75277 · Managing Editor
    Receive manuscriptBy Managing Editor
  3. Review manuscript

    Follow the editor's review and decision.

    The Orchard at Low Tide, first editionPRJ-75277 · Managing Editor
    Review manuscriptBy Managing Editor
  4. Prepare content

    Connect owned content and tasks to the project.

    The Orchard at Low Tide, first editionPRJ-75277 · Managing Editor
    Prepare contentBy Managing Editor
  5. Check rights

    Read the agreement term and allowed uses.

    The Orchard at Low Tide, first editionPRJ-75277 · Rights Reviewer
    Check rightsBy Rights Reviewer
  6. Approve content version

    Rights Reviewer decides the selected file version.

    The Orchard at Low Tide, first editionPRJ-75277 · Rights Reviewer
    Approve content versionBy Rights Reviewer
    ApprovalRights Reviewer checks current rights coverage and approves the selected file version.
Inside a record

Carry edition facts onward

Open any project to see its content items, the roles that work on it, its process stages and its approvals on one page.

  1. 1
    Record details

    Owner, Starts at, Due date and Budget.

  2. 2
    Content items

    Each line is linked to this project.

  3. 3
    Who works on it

    Admin, Publishing Director and Managing Editor, each with their own permissions.

  4. 4
    Process stages

    Open project and Prepare content, with the role that acts.

  5. 5
    Approvals

    Approve content version, with who decides.

Project PipelineThe Orchard at Low Tide, first edition
Publishing House ERP · Projects

The Orchard at Low Tide, first edition

Planned

Log activity
1
Record details
OwnerLeila Mercer
Starts at15 Nov
Due date19 Nov
Budget870
2
Content items

The Orchard at Low Tide, first edition

TitleStatusOwner
The Orchard at Low Tide, chapter proofsDraftMalik Chen
Author interview for spring catalogEditingSofia Neri
Back cover copy for Cedar Meets RainReviewTariq Banerji
Content items
6
3

Who works on it

  • AdminManage Users, People
  • Publishing DirectorManage Projects
  • Managing EditorManage Manuscripts, content items
4

Process stages

  • Open projectPublishing Director
  • Prepare contentManaging Editor
5

Approvals

  • Approve content versionRights Reviewer
    Approved
Example screen with sample data
Approvals

Approve the right file version

A rights agreement review and a content version approval need an identified person. Bind the approver's People record to their user before the first approval.

OverviewApprovals
Publishing House ERP · Overview

Approvals

Signed in as Rights Reviewer

Waiting for you

4 To review1 Overdue2 Decided todayOnly mine
0 selectedApproveReturn
  • CI-92605The Orchard at Low Tide, chapter proofs
    The Orchard at Low Tide, first editionRequested by Jonah Okafor
    Review2dActions
  • CI-43084Author interview for spring catalog
    The Orchard at Low Tide, first editionRequested by Malik Chen
    Review2dActions
  • CI-17360Back cover copy for Cedar Meets Rain
    The Glasshouse Letters, illustrated editionRequested by Tariq Banerji
    Review5dActions
  • CI-42953Glasshouse illustration captions
    Where Cedar Meets Rain, fall listRequested by Malik Chen
    Review4dActions

Who approves what

DecisionApprover
Approve content versionRights Reviewer decides the selected file version.Rights Reviewer
Approve content files, content itemsRights Reviewer
2 approval rules · set per role in Proto
Example screen with sample data
Roles

A workspace for each role

Everyone opens Publishing House ERP to the work that is theirs. Pick a role to see what it starts with.

Admin

Maintains access and reference records for the publishing team.

  • Manage Users, People
  • View Projects, Manuscripts, content items, rights agreements, print editions, production tasks, project costs, content files, approval operations
Reports

See the work behind each title

Read editorial progress, rights dates, edition records and project costs from operating data.

Overview
Publishing House ERP · Overview

Publishing House ERP dashboard

This quarter

Manuscripts in view
6
Submitted
6

Projects by status

How far records got this quarter

StageReachedStep
Planned27
Approved1141%
In production545%
Review120%

Budget by status

Sample totals per stage

1.0k0
-3000Planned
-1000Approved
0In production
1.0kReview
-3000Delivered
Example screen with sample data
  1. 01Manuscripts by editorial status

    Count submissions by Status and Editor.

  2. 02Editorial intake by date

    Review submitted at and the status of manuscripts received in a period.

  3. 03Content deadlines

    Show each content item's due at, Owner and Status by Project.

  4. 04Production task backlog

    Group unfinished production tasks by Project, assigned to and Status.

  5. 05Rights term review

    Show rights agreements by ends at, Content and party name.

  6. 06Print edition register

    Group print editions by Manuscript with ISBN, edition number and release date.

  7. 07Project cost position

    Sum project cost amount by Project, Category and Status alongside project budget.

  8. 08Approved file history

    Show content file version, uploaded at, Content and approved by.

Controls

Keep rights and approval linked

Each stage, from manuscript to approved content, names the role that acts and the status it records, so a change is never anonymous.

OverviewFrom manuscript to approved content
Publishing House ERP · Process

From manuscript to approved content

Each stage, the role that acts and the status it records

Process stages
10
Approval steps
1
Roles involved
4
Tables touched
8
Review manuscript
Managing Editor
StatusSubmitted → Review
Decide manuscript
Managing Editor
StatusReview → Accepted
Prepare content
Managing Editor
StatusDraft → Editing
RecordsContent items, Projects, People
From manuscript to approved content
  1. Start
    Review manuscriptSubmitted → Review
    Managing Editor
  2. Step
    Decide manuscriptReview → Accepted
    Managing Editor
  3. Step
    Prepare contentDraft → Editing
    Content items
  4. Step
    Coordinate tasksOpen → in progress → Review → Completed
    Production tasks
  5. Approval
    Check rightsRights Reviewer
    Rights agreements
Example screen with sample data
AI agent

Ask Proto about the next handoff

Ask Proto to help locate title work and prepare decisions for the right person.

It can

  • Managing Editor: Show manuscripts in review with their editor and submission date, then find content items due on the same title.
  • Production Lead: List open tasks by project and assignee, and show edition facts linked to the manuscript.
  • Rights Reviewer: Find the agreement attached to a content item and its term before opening the version for approval.
  • Finance Lead: Summarize project costs by category and status alongside the title budget.

Stays with a person

  • A person decides whether a manuscript is accepted, whether a rights agreement covers the intended use and whether a content file version is approved.
  • The assistant can prepare the records and show the linked evidence; the named reviewer makes the decision.
  • A printer or distributor confirms its own downstream work.
Integrations

Connects to the tools you use

Set up connections through ERP.AI and Proto workflows, with every change logged.

  • Publishing House ERP
  • Printer
  • Distributor or retailer
  • Finance system
  • File storage
Data model

Your data, in tables you can change

Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.

Browse all 11 tables
11tables
  • Publishing projects5
  • Manuscript review3
  • Content production5
  • Rights and approval5
  • Print editions3
  • Costs and reporting4
Implementation

Roll out one team at a time

Start with one team and one process, then add the rest once the basics are running.

  1. Agree title ownership

    Name the Publishing Director, Managing Editor, Production Lead, Rights Reviewer and Finance Lead. Confirm the person who makes the version approval has a People record bound to a user.

  2. Load the first records

    Set up one project, its owner and budget. Add a manuscript with editor, content items, production tasks, rights agreement, file version and a project cost.

  3. Rehearse the decision

    Record the manuscript review decision. Put a content item in review, check the agreement term and approve the selected file version with the named reviewer.

  4. Check the handoffs

    Read the print edition and project cost views. Confirm the next owner can identify the same title and explain any remaining work.

Pricing

$0per user

The base account and everyday work in the ERP.AI app are free, for every user.

  • No per-user or per-seat fees
  • Viewing, editing, approving and exporting records in the app is free
  • Pay only for machine work: API calls, imports, workflows and AI agents
  • Prepaid credits from $5. Purchased credits never expire

Pricing details

Machine work rate card Included per $1

Machine work rate card
UsagePer $1
Record reads (list, filter, get)20,000
Search or aggregate queries4,000
Record writes4,000
Imported or synced records200,000
Workflow runs2,000
AI agent runs2,000
Scheduled jobs or webhooks20,000
File uploads (MB)2,000
CSV or PDF exports100
FAQ

Questions, answered

Scope, rollout and pricing for Publishing House ERP.

All questions
How do I get started?

Click Get started, then use Proto to configure Publishing House ERP for your business. Start with one title, its project owner, a manuscript, a content item, a rights agreement and a production task. Rehearse the version approval with the intended reviewer.

What does a publishing project hold?

It holds the title's owner, start and due dates, budget and status. Content items, production tasks and costs link back to that project.

How are manuscripts followed?

A manuscript records its title, author, submission date, editor and editorial status. Managing Editor can follow the submitted and reviewing work in the saved lists.

Where does content production happen?

Content Items show the work on a status board with the owner, project and due date. The selected record opens in an inspector; production tasks show assigned work separately.

Who approves a content version?

Rights Reviewer checks the current agreement and selected file version. The approval records the person on the file and changes the linked content item's status when the check succeeds.

How do we see rights dates?

Rights agreements hold start and end dates, allowed uses, party and contract. The rights term views help the reviewer find agreements that need attention.

Where are ISBN and edition details kept?

Print Editions List shows the ISBN, edition number, print quantity, release date and linked manuscript.

Can we compare costs with a title budget?

Project costs have category, date, amount and status. Read those entries alongside the budget on the project, using a consistent cutoff and status scope.

How does distribution receive the title details?

Agree a connection and owner for the handoff to your distributor or retailer. The edition and content records provide the identifiers and approved material to check before sending.

Set up Publishing House ERP your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started

A personal agent for your business

Get started with Proto

Your app is selected. Download Proto, then open it with this context.

Selected appPublishing House ERP

Choose your computer’s platform.

Download Proto

Install Proto, then return to this panel.

Already installed? Open Proto

Free to use. Your own model provider may charge for usage.