Apps & team access
Create apps, invite teammates and choose which apps each collaborator can manage. Your app separately controls access for its own users.
Business capabilities, ready for your app.
Explore what Piezas provides, what our engineers manage, and what each capability makes possible for your business.
AI & connected tools
Let AI work with your app, answer from your knowledge and connect the tools you already use.
Built-in AI access (MCP)Connect an AI assistant to find and update business records, manage tasks and move work forward in your app.
For example
ask your connected assistant to find a customer, update their record and create a follow-up task.
What’s included — and why it matters
Tools based on your business records
Create AI tools from your app's record types to find, view, add, update or delete records.
Why it matters
The assistant can work with the business information your app actually uses.
Pipeline actions
Let a connected assistant list pipelines, read their boards and move existing items between stages.
Why it matters
People can move work forward through a conversation.
Tasks from a conversation
Let the assistant list, create and update tasks, including their owners, deadlines and priorities.
Why it matters
Turn a request into a trackable next step.
A standard AI connection
Use MCP, a shared way for compatible AI assistants to understand and call an app's tools.
Why it matters
Add AI access without designing a separate tool connection from scratch.
What Piezas manages
- MCP connection handling and discovery of tools from your record types.
- Ready-made tool adapters for business records, pipelines and tasks.
What you choose
- Which compatible assistant to connect to your app.
- The protected server connection and the app's access rules.
What to expect: Enable MCP through a protected server connection in your app. The included tools cover business records, pipeline actions and tasks; your app controls access.
Knowledge Base & AI answers (RAG)Give your app answers grounded in your own documents, with sources people can check.
For example
a team asks about your procedures and gets an answer alongside the relevant passages from your documents.
What’s included — and why it matters
Your documents and reference material
Add supported PDFs, Word documents, text, web pages and other text-based files to collections.
Why it matters
Give your app a defined body of business knowledge to draw from.
Automatic preparation for AI
Extract text, split it into useful passages and build an index for meaning-based search.
Why it matters
Your app does not have to build its own document-to-search pipeline.
Search by meaning
Find relevant passages even when a question uses different wording from the source.
Why it matters
People do not have to guess the exact words in a document.
Answers with source references
Find relevant material before asking AI to answer, a process called retrieval-augmented generation, or RAG.
Why it matters
People can review the source passages behind an answer.
Collection and processing controls
Track whether material is ready and remove documents and their search entries when needed.
Why it matters
Keep control of the knowledge your app uses.
What Piezas manages
- Document parsing, passage preparation, search indexing and retrieval.
- Answer generation using retrieved passages and returned source references.
What you choose
- The material to include, its accuracy and who can use it.
- Your connected OpenAI account and the answer experience in your app.
What to expect: Requires a connected OpenAI account. Use documents with readable text; scanned pages need document processing first. Important answers should be checked against their sources.
IntegrationsLet your app work with the business tools you already use, with connection credentials managed by Piezas.
For example
create a Google Calendar event, update a HubSpot contact or prepare a QuickBooks invoice from your app.
What’s included — and why it matters
Actions in connected business tools
Use supported calendar, email, customer-management, accounting, meeting and document actions.
Why it matters
Connect your app to the systems your business already depends on.
Protected connection credentials
Keep provider credentials encrypted and separate from your app's code.
Why it matters
Your app can use a connection without carrying the provider's secrets.
Connection renewal
Renew supported connections when their temporary access is about to expire.
Why it matters
Reduce the connection maintenance your app must implement.
Limited access for each process
Allow selected actions through a connection, with optional expiry and revocation.
Why it matters
Give a process the access it needs without sharing unrestricted credentials.
Connection checks and activity
Check connection status and record supported actions as they run.
Why it matters
Have information to consult when a connected process needs attention.
What Piezas manages
- Encrypted connection storage, supported renewal and provider actions.
- Connection checks, selected-action permissions and activity records.
What you choose
- The tools and accounts to connect, including their required permissions.
- Any required provider credentials, subscriptions and setup.
- How information in each tool relates to your business records.
What to expect: Supported connections include Google Calendar, Drive, Gmail, Zoom, HubSpot, DocuSign and QuickBooks, plus AWS Textract through a configured processing service. Available actions and account requirements vary by tool.
People & information
Give people access and keep the information your business runs on organized.
Users & sign-inGive people accounts with the protection and recovery tools a real app needs.
For example
a staff portal where team members enter an extra code before viewing customer work.
What’s included — and why it matters
Accounts and email verification
Create accounts, sign people in and confirm that they control their email address.
Why it matters
Start with an account flow that covers more than a password box.
Enforced multi-factor authentication (MFA)
Require an extra verification step when people sign in to your app, using an authenticator app or a verified email address.
Why it matters
An extra check helps protect an account if its password is stolen.
Password recovery
Let people reset a forgotten password and end their old sign-in sessions.
Why it matters
People can regain access while old sessions stop working.
Sign-in protection settings
Set how long sign-in lasts and when repeated failed attempts trigger a lockout.
Why it matters
Match the protection level to the way your app is used.
Account disabling
Disable an account and revoke its active sessions.
Why it matters
Remove access when someone should no longer use the app.
Sign-in activity records
Keep records of important account and sign-in events.
Why it matters
Have a history to consult when investigating access problems.
What Piezas manages
- Account, sign-in, verification and recovery behavior.
- Enforced MFA, session controls and account event records.
What you choose
- Who can create an account and how sign-up looks.
- Session duration and protection against repeated failed sign-in attempts.
- What each person is allowed to see and do in your app.
What to expect: Piezas handles sign-in. Your app determines what each person may see and do after signing in.
Business recordsOrganize customers, jobs, requests and the other information your business works with.
For example
customer records linked to their jobs, with the latest activity kept alongside them.
What’s included — and why it matters
Your own record types
Define the information each customer, job or other record should contain.
Why it matters
Your data can reflect your business instead of a fixed spreadsheet template.
Ready-made business record patterns
Start from reusable structures for contacts, companies, projects, bookings, invoices, expenses and more.
Why it matters
Begin with familiar business information instead of defining every field from scratch.
Checks on saved information
Check records against the field structure you define.
Why it matters
Catch mismatched information before it becomes harder to use.
Relationships and activity
Link related records and store the activity your app supplies.
Why it matters
Keep the context behind a customer or piece of work in one place.
Search, import and export
Find stored records and move record data into or out of your app.
Why it matters
Make existing information useful without starting from an empty app.
What Piezas manages
- Reusable record patterns, storage, field validation and relationships.
- Search, data transfer and supplied activity records.
What you choose
- The types of records, fields and relationships your business needs.
- The screens, business rules and access permissions around them.
- Which activities your app records in the timeline.
Files & documentsKeep business files organized, connected to the right work and easy to trace.
For example
a customer folder containing proposals, supporting files and earlier document versions.
What’s included — and why it matters
Files, folders and labels
Store files in folders and add labels that help organize them.
Why it matters
People can find the right material without chasing scattered attachments.
Document versions
Keep track of different versions of a document.
Why it matters
Understand which version belongs to a piece of work.
Links to business records
Attach documents to the customer, job or other record they belong to.
Why it matters
The file stays with its business context.
Temporary file access links
Provide time-limited links for uploading and downloading files.
Why it matters
Share access to the file without putting storage credentials in your app.
What Piezas manages
- File organization, version records and connections to business records.
- File storage access and temporary upload and download links.
What you choose
- Which files to collect, how to organize them and who can access them.
- The upload, download and document screens people use.
Documents & content
Read information from paperwork, collect signatures and publish useful content.
Document processing (OCR)Read information from uploaded paperwork and keep processing results connected to the original document.
For example
start analysis of an uploaded form and keep the returned fields and confidence information ready for review.
What’s included — and why it matters
Read forms and tables
Start document analysis through AWS Textract to recognize text and information in forms and tables.
Why it matters
Use OCR, or optical character recognition, to reduce retyping information from paperwork.
Structured extraction results
Store returned information as fields your app can work with, alongside the extraction request.
Why it matters
Use reviewed results in your business process instead of leaving them inside a file.
Confidence and review context
Keep provider-supplied confidence information and a link to the source document.
Why it matters
Give people the context they need to check uncertain results.
Processing history
Track each job's progress, reported errors and completion.
Why it matters
Know which documents are ready and which need attention.
What Piezas manages
- Document-analysis requests through a configured provider.
- Job records, returned results, confidence information and document links.
What you choose
- The documents to process and how reviewed results are used.
- Provider setup and the connected step that collects completed results.
What to expect: Requires a configured document-analysis provider and a connection that collects its results. Your app decides how people review and use the extracted information.
E-signaturesSend documents for signing through a connected provider and keep each request with the work it belongs to.
For example
send a service agreement to two named signers in order and track the request alongside the customer's record.
What’s included — and why it matters
Named signers and signing order
Specify who needs to sign and the order in which they should receive the request.
Why it matters
Make the intended signing process clear.
Send through DocuSign
Create and send a signing request through a configured DocuSign connection.
Why it matters
Use an established signing service without rebuilding its request integration.
Request and signer status
Keep the provider's request reference and reported signing status with the document.
Why it matters
See which agreement a signing request belongs to and follow its progress.
Connection to the signed file
Record the completed document and link it back to the original request.
Why it matters
Keep the result with its business context.
What Piezas manages
- Signing request records and dispatch through the configured provider.
- Signer details, reported status and links to the signed document.
What you choose
- The document, signers, signing order and provider account.
- The connected steps that collect completion status and the signed file.
What to expect: Requires a configured signing provider. Completion updates and the signed file are supplied through your connected process.
Articles & publishingGive help articles, business updates and reference content a home inside your app.
For example
prepare a help article as a draft, publish it when ready and display it on your app's help page.
What’s included — and why it matters
Structured article content
Store titles, formatted and plain text, categories and authors.
Why it matters
Keep content organized separately from the screens that display it.
Draft and published states
Keep track of whether an article is a draft or published, including its publication time.
Why it matters
Let your app distinguish work in progress from content ready to show.
Readable article addresses
Generate a unique name for each article that your app can use in a page address.
Why it matters
Give people useful, recognizable links to content.
Publication events
Signal when an article is published so a connected action can respond.
Why it matters
Connect publishing to a notification or another step in your app.
What Piezas manages
- Article records, categories, authors and publishing state.
- Generated article addresses and publication events.
What you choose
- The content, editing experience and who may publish.
- The pages that display articles and who may read them.
Work & collaboration
Keep work moving, make responsibilities clear and connect the next step.
PipelinesSee where every opportunity or request stands in your process.
For example
follow a customer inquiry from new lead to proposal to won or lost.
What’s included — and why it matters
Stages that fit your process
Choose the stages and outcomes used to organize your work.
Why it matters
Your app can follow the steps your team actually uses.
Items grouped by stage
Get the items at each stage for a board or another view in your app.
Why it matters
See what is waiting, moving or complete.
Movement history
Record stage changes and the time spent in the previous stage.
Why it matters
Understand how work progressed and where it may be slowing down.
Stage totals and values
Summarize how many items and how much recorded value sit at each stage.
Why it matters
Get a clearer picture of workload or opportunity value.
What Piezas manages
- Stage validation, item records and movement history.
- Stage grouping, totals and recorded time calculations.
What you choose
- Your stages, outcomes and the records moving through them.
- The board, screens and actions your team uses.
TasksKeep track of what needs doing, who owns it and when it is due.
For example
assign a follow-up to a teammate and create the next weekly task when this one is finished.
What’s included — and why it matters
Assignments and priorities
Give tasks an owner, priority and due date.
Why it matters
Make responsibility and urgency clear.
Overdue detection
Identify open tasks whose deadlines have passed.
Why it matters
Bring work that needs attention back into view.
Recurring tasks
Create the next recurring task when the current one is completed.
Why it matters
Routine work does not need to be entered again each time.
Lists, comments and record links
Group tasks and keep comments and related business records with them.
Why it matters
People can understand the work without reconstructing its context.
What Piezas manages
- Task records, completion, reopening and recurrence.
- Overdue checks and events that your app can respond to.
What you choose
- Owners, deadlines, priorities and recurring schedules.
- Which alerts or other actions should follow a task event.
What to expect: Overdue detection identifies the event. Sending an email or taking another action needs a connected follow-up step.
Workflows & automationConnect business events to the next step in your process.
For example
when a request meets your chosen conditions, call a connected action to start its next step.
What’s included — and why it matters
Event rules and conditions
Run a configured action when an event matches the conditions you choose.
Why it matters
Move routine decisions out of repeated manual checks.
Recurring schedules
Trigger connected work at chosen intervals or times.
Why it matters
Scheduled work can start without someone keeping the app open.
Connected actions
Call configured services or app actions as the next step.
Why it matters
Join separate parts of a process together.
Execution history and scheduled retries
Record rule results and retry scheduled deliveries after temporary failures.
Why it matters
See what ran and investigate what needs attention.
What Piezas manages
- Rule evaluation, recurring schedules and execution records.
- Delivery and retries for configured scheduled actions.
What you choose
- Which business events, conditions and timing matter.
- The connected actions that perform each step and what they do.
What to expect: Each action needs a configured connection. Piezas runs the rules and schedules; the connected action performs your business task.
DiscussionsKeep conversations beside the work they are about.
For example
discuss a customer request in a thread attached to that request.
What’s included — and why it matters
Threads linked to records
Keep messages connected to a customer, request or other business record.
Why it matters
Decisions stay with the work instead of disappearing into separate chats.
Channels
Organize ongoing conversations into named channels.
Why it matters
Give related discussions a clear home.
Mentions, reactions and attachments
Mention people, acknowledge messages and include supporting material.
Why it matters
Make it easier to ask for input and share context.
Channel archiving
Remove an old channel from active use while retaining its discussions.
Why it matters
Keep the workspace tidy without losing its history.
What Piezas manages
- Stored threads, channels, messages, mentions and reactions.
- Channel archives and events for new comments or mentions.
What you choose
- Conversation screens, channel organization and access rules.
- Whether mention events should produce email or other alerts.
Customers & communication
Collect information, arrange appointments and keep people informed.
Forms & submissionsCollect information from customers or teammates and keep their submissions organized.
For example
accept a service request and track its submission as your team follows up.
What’s included — and why it matters
Reusable form definitions
Define the questions and information a form should collect.
Why it matters
Keep the structure of incoming information consistent.
Required-answer checks
Check that required answers are present when a form is submitted.
Why it matters
Reduce follow-up caused by missing essentials.
Public submissions
Accept submissions to active forms without requiring the visitor to sign in.
Why it matters
Let customers take the first step with less friction.
Submission records and status
Store submissions, track their status and produce events for follow-up.
Why it matters
Give each response a place in your process.
What Piezas manages
- Form definitions, required-answer checks and submission storage.
- Submission status records and events your app can use.
What you choose
- Questions, form screens and who can review responses.
- The follow-up actions and any additional spam protection.
Calendar & bookingsLet people book time that fits your availability.
For example
offer appointment slots with time between meetings and a minimum notice period.
What’s included — and why it matters
Availability rules
Set working hours, date-specific exceptions and time zones.
Why it matters
Offer times that fit the way your business operates.
Practical booking limits
Set gaps between appointments, advance notice and how far ahead people can book.
Why it matters
Avoid appointments that leave too little time to prepare.
Booking and conflict checks
Create, reschedule or cancel bookings and reject overlaps with existing Piezas bookings.
Why it matters
Keep appointment records current and reduce double booking.
Reminder events and connected calendars
Trigger reminder events and check busy times from a connected Google Calendar.
Why it matters
Support timely reminders and account for time booked elsewhere.
What Piezas manages
- Availability calculations, booking records and overlap checks.
- Reminder-event scheduling and connected calendar busy-time checks.
What you choose
- Availability, booking rules and the screens customers use.
- Calendar connections, reminder timing and message delivery.
What to expect: External calendar checks need a connected account. Reminder emails need a configured delivery step, and public booking flows must use the availability check.
Email notificationsSend the individual emails people expect from your app.
For example
send a booking confirmation containing the customer's name and appointment details.
What’s included — and why it matters
Individual app emails
Send confirmations, reminders and alerts to one recipient at a time.
Why it matters
Keep people informed after an action in your app.
Reusable, personalized templates
Add names and other supplied details to saved message templates.
Why it matters
Keep routine messages consistent without making every email identical.
Message history and status
Record sends, failures and delivery updates supplied by the email provider.
Why it matters
Have a record to inspect when someone reports a missing message.
Email usage tracking
Track recent sends against the applicable daily allowance.
Why it matters
See when your app is approaching its sending limit.
What Piezas manages
- Template rendering, calls to the configured email sender and message records.
- Sending limits and processing of provider delivery updates.
What you choose
- Recipients, message content and the events that send an email.
- Sender identity and any required email-provider setup.
What to expect: For individual app emails, not bulk campaigns. Sending limits apply, and a recorded send is not a guarantee of delivery.
Campaigns & follow-up plansKeep customer campaigns, follow-up plans and their participants organized.
For example
store an onboarding follow-up plan and track which customer records have joined it.
What’s included — and why it matters
Campaign definitions
Store campaign details, intended audience settings and content references.
Why it matters
Keep the plan for a customer communication in one place.
Reusable sequence plans
Save the steps that make up a follow-up series.
Why it matters
Give your sending setup a consistent plan to work from.
Enrollment records
Track which business records have joined or left a sequence.
Why it matters
Know who belongs in each follow-up plan.
Events for connected actions
Produce events when campaign or enrollment actions take place.
Why it matters
Connect campaign organization to the rest of your app.
What Piezas manages
- Storage of campaign plans, sequence definitions and enrollment records.
- Campaign and enrollment events for connected services.
What you choose
- Content, audiences and the order of follow-up steps.
- The sending service and setup that deliver and advance the sequence.
What to expect: This capability organizes campaign and sequence records. Message delivery and automatic follow-up execution require a separate sending service and setup.
Business operations
Organize commercial details and keep report settings and results together.
Products, pricing & quotesKeep what you sell, what it costs and the details of each quote or invoice together.
For example
prepare a service quote with line items, a discount and the tax rate your business supplies.
What’s included — and why it matters
Product and service catalog
Store the items and pricing information your app sells or quotes.
Why it matters
Reuse commercial details instead of entering them from scratch.
Quotes and invoice records
Create records for quotes, proposals, estimates and invoices.
Why it matters
Keep the commercial documents behind your work organized.
Line items and discounts
Build up a quote or invoice from individual items and supplied discounts.
Why it matters
Make the price breakdown clear and reusable.
Recalculated totals
Calculate totals using the item values, discounts and tax rates you supply.
Why it matters
Reduce repeated arithmetic when commercial details change.
What Piezas manages
- Catalog and commercial document records, including their line items.
- Total calculations using the prices, discounts and tax rates supplied.
What you choose
- Products, prices, discounts and the correct tax rates for your business.
- Document screens, delivery and any payment-service connection.
What to expect: This capability does not process payments or determine which taxes apply. Your app supplies those business decisions and any document-delivery steps.
Reports & dashboardsKeep report settings, dashboard layouts and saved results together.
For example
save the layout of a weekly dashboard and a snapshot of results supplied by your app.
What’s included — and why it matters
Report definitions
Store the settings that describe a report in your app.
Why it matters
Reuse the same report configuration over time.
Dashboard layouts
Save how the sections of a dashboard should be arranged.
Why it matters
Keep the view consistent when people return to it.
Saved snapshots
Store report results supplied by your app as snapshots.
Why it matters
Retain a result to refer to later.
What Piezas manages
- Storage of report definitions and dashboard layouts.
- Storage of the report snapshots your app supplies.
What you choose
- Which business questions the reports should answer.
- Data collection, calculations, charts and the report screens.
What to expect: Your app supplies the report data and charts. Piezas stores layouts, report settings and saved snapshots.
Behind every capability
The foundation is managed, too.
Shared business settings
Keep organization settings in one place for your apps and business capabilities to use.
Managed app hosting
Publish your app on Piezas Cloud with a secure web address. Piezas operates the hosting; your app's custom code remains part of your app to maintain.
Build with these capabilities.
Your AI connects the capabilities and creates the screens and flows that fit your business.