Why Made with Pepper
One platform.
Your way of working.
Use the parts you need. Connect more of the work when it helps. Keep the software, the data and the decisions in your hands.
Start with one useful job
The next tool should know the work.
Start by sending an invoice. When you need a project, tasks or time tracking, use the same customer record. The work can grow without becoming a second set of disconnected details.
In this example, Kindred’s team can see the project, the hours and what still needs to be invoiced in one place.
Follow the hours into an invoiceHow the records stay connected
Follow the agreement.
Quotes, milestones and invoice drafts keep their references. You can trace a customer’s balance back to the work.
Keep the original.
Issued invoices stay intact. Credits and recorded payments explain changes to the balance; receipts stay with purchases.
Choose your tools.
Use Pepper’s screens or an optional connected AI client with permitted access. The same records remain the source, and you confirm invoice issuance.
- On their screenChoose a service
The customer tells you what they need.
- In PepperReview the request
The choices stay with the enquiry.
- Your next stepPrepare the quote
Your team checks the work and the price.
A connection beyond your team
Give your customers a way in.
Your website can collect an enquiry and bring it into Pepper. The customer gets a simple form; your team gets a record to act on.
That is the idea behind widgets: useful services on an existing website, behind a button or at a shared link.
Picture the customer servicesCould I offer services to clients?
A customer workspace lets a client manage its widgets and team within the plan and access you assign. Your licence permits selling widget access to multiple businesses on one production installation.
You invite each business and assign its plan. These accounts cover widget services; the licence does not permit software resale.
Explore the agency pathBuild on something you own
Your business.
Still yours.
You hold the installed copy, the database and the full source. Your downloaded software keeps working when access to updates and support ends.
Keep using it.
Your licence never expires. Renewal buys updates and support; it does not keep your installed copy switched on.
Make it fit.
Read, change and maintain the full source for your licensed installation. The commercial licence prohibits redistribution.
Keep the keys.
Choose where it runs and who maintains it. Hosting, email, security and backups are yours to arrange.
What control means in practice
- Your server and region
- Choose hosting that meets Pepper’s requirements, including the country where your installation and backups live. The download includes a Docker setup. Ask your host which law applies to its servers.
- Your keys and access
- Keep the application key, administrator accounts, domain and backups in your control. Give your technical partner the access they need to maintain the installation.
- Your exit
- Export records, settings and files from the browser. Import them into a fresh, compatible Pepper installation. A Laravel developer can take over with the source and the manual.
Choose who runs it
Ownership comes
with upkeep.
You or a technical partner handle the server, updates, email and backups. Product support helps with Pepper; it does not operate your hosting.
The manual explains installation and routine maintenance.
Plan the practical sideExplore custom development and maintenanceBefore you decide
Know what you
depend on.
Four questions worth asking of any tool your business relies on.
Check your software dependenciesWhat happens if I stop renewing?
Your Pepper licence never expires. Cancelling update and support renewal stops future charges; you keep the full paid period and can continue using your downloaded copy. Hosting and upkeep remain separate.
Read the purchase termsCan I take the records with me?
Try an export and check the records, files and history your business needs. Pepper’s full export can move them to a compatible Pepper installation. It does not promise an automatic migration into another product.
Check the exit planWho can connect other tools?
You choose optional MCP or HTTP connections and the access they receive. Current permissions still apply. Pepper needs no AI account; a chosen AI provider is a separate service. You confirm invoice issuance in Pepper.
See the controls for AI connectionsWho looks after recovery and data?
You or your technical partner choose the host and backup location, manage security and email, and test restores. Keep backups apart from the live server. Check which companies can access the infrastructure and which laws apply.
Plan the upkeep