Penta · Business discovery agent

Turn what your business knows into delivery work your team can start on.

Talk, upload or type. Penta analyses it, ties it to your strategy, and drafts Epics, Features and Stories for review. Nothing reaches Jira until a person approves it.

Licensed software · invite-only testing

Example EpicAwaiting review

Automate supplier order intake

"We re-type every order from the email into the spreadsheet." Interview, 14:32

Serves
Objective: cut order handling time
Outcome
Human-assisted automation
Confidence
Medium two assumptions to validate
Needs
Mailbox access, order spreadsheet
ApproveEditRejectRegenerate
The problem

Backlogs start as conversations, and the reasons get lost.

Workshop notes, slide decks, voice memos and half-remembered goals rarely become a backlog the same way twice. It depends on who was in the room.

Work without evidence

Items get written up with nothing to show where they came from, so nobody can say later why they were proposed.

Work without a goal

Teams build things no objective asked for, because the link to strategy was never made.

Work without a check

Generated text goes straight into the tracker. Fixing it afterwards costs more than reviewing it first.

How it works

Five stages, with a person in charge of each.

Penta does the drafting. Your people decide what is true, what is worth doing, and what goes to Jira.

  1. 1

    Context

    Add what you know in any mix: typed notes, documents (PDF, Word, text, images) and recordings. Recordings are transcribed, and you can correct the transcript. Choose the strategy and objectives the assessment is for.

    Contributors can do this stage
  2. 2

    Assessment

    Penta writes a structured business assessment: operating context, current processes, problems and bottlenecks, desired outcomes, data and integration needs, constraints and risks. It separates confirmed facts from assumptions and open questions, and asks follow-up questions where something is missing or contradicts something else. Every section is editable.

  3. 3

    Solution & Plan

    Each opportunity is classified, and some are told plainly that automation is the wrong answer. See the four outcomes below.

    Reviewers and above
  4. 4

    Generate Work

    Penta drafts Epics with the evidence behind each. Features are proposed first, then the Stories of each Feature you accept. Output is sized to the note: a short note produces a first step, not an invented programme, and what is over is held back. Edit, reject, regenerate, merge or approve each item, one at a time or in bulk.

    Reviewers and above
  5. 5

    Jira Handoff

    You see exactly what Jira will receive. A publisher confirms, and Penta creates the approved items in your Jira project as that person. It records the Jira keys, the time and the publisher. If an item fails, it can be retried without duplicating the ones that worked. Exports are available too.

    Publishers
Solution & Plan

Not every problem needs automation.

For each candidate process, Penta recommends one of four outcomes, and says why.

Full automation

Frequent, repeatable work with the data available and few exceptions.

Human-assisted automation

The machine prepares and a person decides, where judgement or exceptions matter.

Process improvement

A simpler process fixes it. No software needed.

Stay human-led

The work depends on judgement, trust or relationships that automation would damage.

The recommendation weighs frequency, volume, repeatability, data availability, integration feasibility, business value, delivery complexity, exception handling, risk and the human judgement required. Estimates are qualitative and labelled as such. They are not commitments or forecasts.

What an Epic carries

Every Epic shows its working.

  • Name and concise summary
  • Business problem
  • Objective and intended outcome
  • Proposed automation
  • In-scope activities
  • Explicit exclusions
  • Expected benefits
  • Required data and sources
  • Required integrations
  • Dependencies
  • Delivery and operational risks
  • Assumptions to validate
  • Value and complexity estimates
  • Confidence level
  • Success measures
  • High-level acceptance criteria
  • Strategy horizon and place in the strategy tree
  • References to the interview evidence
Strategy built in

Every story traces back to the goal it serves.

Penta keeps your strategies, objectives and key results in Strategy & Ideas. Work is generated against them and stays linked to them.

Example only. Your own strategies, objectives and key results replace these.

Chosen at the start

Select the strategy and objectives when you begin an assessment. Each suggested Epic says which objectives it serves and why.

Suggestions, not changes

Penta can propose new strategy items from your notes, documents and Epics. They stay suggestions until someone with the right to manage strategy accepts them.

Home shows the picture

Programme status, the strategy tree, what is at risk, and the dependencies delaying each strategy item.

Find and ask

Search, or ask a question and get an answer with its sources.

Search

One box in the top bar finds assessments, Epics and strategy items across your workspace.

Ask AI

Ask in plain words and the answer appears in a panel, as a conversation. It reads your assessments, notes, recordings and documents, read-only, and quotes them word for word so you can check it. If the AI service is unavailable, it says so and why.

Built for control

A person approves everything that matters.

Penta never changes Jira on its own. Publishing needs an explicit final confirmation from someone with the Publisher role.

RoleCan do
ContributorCreate and work on assessments they can see, and add context. Share their own.
ReviewerEverything a Contributor can, plus review, edit and approve drafts.
PublisherEverything a Reviewer can, plus send approved work to Jira.
AdministratorEverything above, plus manage people, read the audit log and see every assessment in the workspace.

Roles enforced on the server

The app only shows what your role allows, and the server checks every request anyway. A person can hold several roles.

Private until shared

An assessment is visible to its creator, the people it is shared with, and administrators.

Invitation-only sign-in

People sign in with Google or Microsoft. Penta stores no passwords and has no self sign-up. Administrators can remove a person's access and restore it later.

An audit log you can export

Sign-ins, role changes, sharing, access denials and publishing are recorded: who, what, when and the outcome. It never records notes, transcripts, documents or secrets, and it cannot be edited. Administrators export it as CSV.

Separate workspaces

Each client's content is isolated from every other client's. Sepenta platform administrators can set up a workspace but cannot read its content.

Limits against runaway use

AI, transcription and email requests are rate limited per person and per workspace. You get a warning at 80% of the limit before anything is refused.

Your data

Where your content lives, and where it goes.

WhatWhereWhy
Notes, documents, recordings, transcripts, assessments, Epics, Features and StoriesSepenta's Google Cloud project in Belgium (europe-west1): a private database and a private storage bucketTo run the assessment and let you come back to it
The same content, when you run an assessment, transcribe a recording or ask for a draftOpenAI, through its APITo analyse, transcribe and draft
Approved Epics, Features and StoriesYour Jira project, created under the publisher's own Atlassian accountTo start the work
Name and email addressGoogle or Microsoft confirm who signs in; Penta stores the address, name, role and sign-in timesIdentity only. Neither provider sees your mail or files.

Treated as data, not instructions

Text in a note or document is analysed. Instructions hidden inside it are ignored, and answers must fit a fixed structure or they are rejected.

Less sent where less is needed

Suggesting strategy items and breaking an Epic into Features and Stories do not send recordings, names or email addresses.

Deletion

Deleting a recording or a document also removes its stored file. An assessment's owner or an administrator can delete it permanently. Content is not deleted automatically yet; ask us and we will delete a workspace's data.

Requests to OpenAI

Each request to OpenAI is sent with storage turned off.

Part of Sepenta

Penta defines the work. Magnesia runs the delivery.

Penta

Business discovery to reviewed, strategy-linked Jira work.

Magnesia

The delivery console: a programme board built from Jira, standups, repository and hosting health, and delivery reports. Magnesia's agent also answers questions about Penta in Ask AI.

About Magnesia →

Who it is for

For the people who turn talk into a plan.

Business owners and operations leads

You can describe your problems clearly. You do not need to think in Jira or Agile.

Delivery and product managers

You turn conversations into a backlog and want it tied to strategy and checkable.

Consultants

You run structured discovery across several organisations and need each one kept apart.

Leaders

You want to see what each planned piece of work serves, and what is at risk.

Request access

Try Penta on a real problem.

Penta is licensed software and sign-in is by invitation. Tell us who you are and what you would like to plan, and we will be in touch.

Please enter your name.
Please enter a valid email address.
Please choose a product.

By submitting this form you agree to be contacted by Sepenta about your request. We never share your details with third parties. Or write to info@sepenta.io.

Penta is a product of Sepenta. Names and numbers in the examples on this page are illustrative.