We're building Made with Pepper into a full business suite that you run and own. Customers, projects, documents and money should belong to the same business records, with one installation and one database under your control.
Today's product connects customer records, agreed work, invoices, purchases and recorded payments. Invoicing is part of that business, and the starting point for a much wider product. This page separates the released work from what we're building and planning.
Buy for the features available now. Development depends on product sales, revenue and available capacity. Priorities, scope and order can change. There are no release dates or delivery guarantees here, and a purchase does not reserve future features. The product overview, buying answers and purchase terms describe what you can buy.
Released
The demo shows Pepper with example records. The changelog records release history.
The Pepper interface
The website screenshots show the released Pepper interface, with grouped navigation and connected business records.
Customer records, agreed work and billing
Keep customers and contacts with their billing history. Quotes, invoices, proformas and credit notes preserve issued originals. Fixed-price engagements connect scope versions, staff-approved milestones and invoice drafts. See the milestone workflow.
Repeat invoices and recorded payments
Recurring schedules create drafts or issue and send agreed repeat invoices. Staff record money received elsewhere, and reminders use the remaining balance. See monthly service billing and payment corrections.
Purchase evidence and accountant hand-off
Manual purchases hold supplier amounts, categories and receipt files. Calendar month, quarter and year exports include summaries and available source evidence. These exports support your accountant; they do not provide bookkeeping or tax filing. See the purchase hand-off.
Files and related records
Keep uploads in folders, preserve file versions and find their related business records. Permitted staff can create expiring share links. Read the Files manual.
People and access
The staff directory connects people, teams and working hours. Built-in and custom roles, guest scopes and offboarding control access. The People and teams manual explains these procedures. Optional module switches remain owner-controlled; they do not replace account permissions.
MCP and HTTP connections
The owner can connect MCP and HTTP clients with expiring access to permitted records, exact previews and invoice drafts. MCP clients can use browser sign-in. A client can issue one prepared invoice only after the delegated person approves it in Pepper. Clients cannot send, settle or export documents, or change bank and tax settings. No model account is required. See the connection manual.
In development
The next work extends these foundations into the wider suite. No additional product area below is included in this release. Priorities can change; use the changelog to check what has shipped.
The suite we're planning
These are the main areas in the wider plan. They are not included in the current download. We intend to build shared foundations first, then complete useful workflows across the product. The order and final scope can change.
Shared foundations for daily work
The plan includes activity and notifications, comments and mentions, saved views, forms and custom fields. Lists, tables, boards, calendars and timelines would work with the same records. An audit history would let people trace changes across the suite.
Embeddable widgets would bring forms, bookings and other public features to an existing website. A business would not have to replace its site to use them. Each widget depends on the product area that supplies it.
Sales, projects and time
Planned sales pipelines would connect first contact to a customer and an agreed quote. Projects, task boards and time tracking would support delivery; calendars and bookings would bring scheduled work into view. The intended connection runs from the original enquiry through completed work to an invoice draft.
Released engagements cover fixed-price milestones. They do not yet provide this wider project or time-tracking workflow.
Payments, reports and spreadsheets
Online payments and bank-statement matching are planned alongside broader reports and spreadsheets connected to business records. The aim is to trace a figure back to its source and keep a payment consistent wherever it appears.
Today, staff record payments received outside Pepper. There is no payment processing or bank matching in the released product. Accountant hand-off remains separate from bookkeeping and tax filing.
Documents, publishing and email
The plan extends to a document editor, proposals and contracts, electronic signatures, presentations, a website builder and newsletters. Documents could include business records, so a proposal could refer to its quote and a report could show its source figures.
These creation and publishing tools are future work. Existing issued originals and signed document links do not provide a general editor or an electronic-signature service.
Commerce and customer services
An online shop, a customer portal, loyalty and a helpdesk would connect orders and service requests to customer records. A support conversation could refer to the same order and invoice the business already holds.
The public download does not include these areas. Its signed document links do not give customers a login portal.
Automation, mailboxes and an assistant
The plan includes rules, intake flows, connections to the business's own mailboxes and an optional assistant. A person could ask for work in plain language, review the proposed result and finish it in the same application.
The intended rule is that people and agents use the same records, actions and permissions. Anything an agent prepares should remain visible and editable through the interface. Sensitive actions would require human confirmation. The released application has no built-in assistant or active customer-data suggestions.
One product, connected records
The direction is one package whose shipped areas share customers, people, files and history. A business should be able to start with the work it needs and use another shipped area without rebuilding its records or buying separate module licenses. Access rules still apply.
That is the product direction, not a promise that today's purchase includes every planned app. Prices may change, and access to future releases follows the purchase and update terms. You keep the installed copy covered by your license.
Use the changelog to check when a planned feature reaches a public release.