Predictability for planning.
Choosing capability and configuring resources helps plan infrastructure, operations and connected services according to use. The organization can review where each task is carried out and how its cost evolves.
Futuramente · The platform we are building
Your organization,
with AI capability of its own.
Connect knowledge, tools and agents to turn requests into reviewed results. Choose how to operate with your data, infrastructure and resources.
From having a need to having capability: technology, integration and support so a useful case becomes a way of working.
Futuramente
A visual reading of the proposal
- What the person brings
A request and its sources
- The proposed work
Work with human review
- What allows work to continue
A version and its record
01 / Capability in service of work
Infrastructure makes it possible.
Work gives it purpose.
Hardware is a means. Value emerges when data, models, software and tools connect to a task the team understands, can review and can continue.
Resources you can govern.
- Configured infrastructure
- The organization’s data and sources
- Chosen models and tools
Technical capability aligned with the organization’s use and decisions.
Bring together what is needed.
- Converse and retrieve context
- Create, coordinate and review
- Preserve sources, versions and decisions
Software and integration so people and agents can work with shared criteria.
From a request to a deliverable.
- Reviewed commercial proposal
- Updated construction report
- Documented intake
Examples of work that retains an owner, approval and evidence of completion.
Direction remains human.People define the objective, review versions and approve actions and commitments.
02 / A foundation for decisions
More control.
Operations that can continue.
Futuramente brings together work on infrastructure, software and integration. The aim is to give the team capability of its own and a stable way to use it as technology evolves.
Decisions about what is yours.
Define which data is used, where it is processed and who has access. Own or dedicated infrastructure is a tool for exercising that control, with permissions and references that accompany the work.
Technology changes.
The work stays connected.
Futuramente aims to buffer the impact of evolving models and tools. Planning those changes helps preserve the process’s criteria, sources and responsibilities while adjusting the capability that supports it.
Local capability, chosen connections. The local core can work with the data, models and tools configured within the organization. Email, WhatsApp, the web and other connected services require the corresponding connectivity.
The vision in concrete situations
A need.
Work that moves forward.
Three fictional stories show how an agent can help prepare and coordinate work. People retain decisions, approval and commitments. The outcomes are illustrative; they do not represent actual executions.
01 / Fictional real estate agencyFrom an inquiry
From an inquiry
to a proposal with context.
The adviser needs to understand the request, compare options and continue the conversation without losing what was agreed.
Human ownerReal estate adviser
Confirms options, conditions, the visit and the proposal before committing to a response.
Support agentPrepare and maintain continuity
Organizes context, gathers references and prepares materials for review.
- 01
Inquiry
A need is received and the interested person’s requirements are clarified.
- 02
Lead and context
The agent prepares the lead record for sales follow-up (CRM), with its permitted references.
- 03
Properties
The adviser compares the options the agent helped gather.
- 04
Visit
The agent proposes arrangements; the adviser confirms the appointment.
- 05
Proposal and review
The agent prepares the draft. The adviser corrects and approves its version.
- 06
Follow-up
The person responsible authorizes the response and defines the next contact.
What completion would look like
An outcome that can be reviewed.
- Document and version
- Commercial proposal v2
- Human approval
- The adviser approves that version before sending it.
- Evidence of completion
- Sent version, response and next task linked to the lead and sales opportunity.
If returned
- Observation
- Correction
- New version
- Human review
If what was approved changes, the new version is approved again.
02 / Fictional property developerA construction issue.
A construction issue.
A decision with references.
The team needs to relate an issue to the drawing and specification, raise a query and leave the decision in an updated report.
Human ownerConstruction technical lead
Assesses the query, decides how to proceed and approves the report update.
Support agentConnect and prepare
Gathers references, prepares the query and organizes follow-up on the decision.
- 01
Construction issue
The team records what needs review and designates the person responsible.
- 02
Drawing and specification
The agent gathers the references and versions the team needs to compare.
- 03
Technical query
A query is prepared with the issue and its sources identified.
- 04
Review and decision
The technical lead reviews the query and records the human decision.
- 05
Updated report
The agent prepares the update. The person responsible reviews and approves its version.
- 06
Follow-up
The team verifies the agreed actions and the person responsible authorizes completion.
What completion would look like
The decision accompanies the document.
- Document and version
- Issue report v2, linked to the reviewed drawing and specification.
- Human approval
- The technical lead approves the report version.
- Evidence of completion
- Decision, references and team verification linked to the approved report.
If returned
- Observation
- Correction
- New version
- Human review
A change needs a new review by the technical lead.
03 / Entirely fictional caseCentro Clínico Ejemplo:
Centro Clínico Ejemplo:
continuity in intake.
The illustrative reference ADM-014 makes it possible to track documents, owners and reviews. The example contains no patient data or clinical information.
Human ownersIntake staff and an authorized professional
Intake staff confirm the documentation; the professional reviews and approves their document.
Support agentOrganize and prepare
Helps identify missing items and prepare materials, without approving or signing on people’s behalf.
- 01
Appointment
The administrative team confirms the arrangements and opens reference ADM-014.
- 02
Missing documents
The agent compares the defined requirements and prepares the list for review.
- 03
Intake
The team confirms which documentation was received and what remains outstanding.
- 04
Document preparation
The appropriate document is prepared for review by the authorized professional.
- 05
Reviewed professional document
The authorized professional reviews, corrects and approves the specific version.
- 06
Administrative follow-up
Intake staff record the outstanding tasks and completion authorized by their lead.
What completion would look like
ADM-014 · fictional reference.
- Document and version
- Professional document v2, associated with ADM-014, with no clinical content in this example.
- Human approval
- An authorized professional reviews and approves that version.
- Evidence of completion
- Received documentation, reviewed version and administrative tasks with an owner.
If returned
- Observation
- Correction
- New version
- Human review
The new version needs review and approval by the authorized professional.
In all three stories, the agent helps prepare and coordinate. Sources, versions, permissions and the work record support continuity; human approval applies to a specific version.
04 / The family is the mechanism
The parts are
in service of work.
For these stories to move forward, conversation, sources, creation, coordination and review are needed. The family organizes those responsibilities and keeps the request connected to its documents and decisions.
People define, review and approve.
The family supports the work; responsibility remains with a named person.
Shared work
- FutureChat
- Converse and interact
A place to formulate the assignment and work with the team.
- FutureDisk
- Preserve sources and versions
Files, originals and versions that can be identified and reviewed.
- FutureCreate
- Create, edit and review
Professional creation and editing with the tools of iMunaCreator.
Continuity and delegation
- FutureMemory
- Resume within boundaries
Permitted context and controlled reuse. Memory supports the work without replacing its sources or authoritative record.
- FutureOps
- Coordinate operations
Agents, workflows and delegated execution to coordinate tasks, people and deliverables.
Policy and evidence
- FutureControl
- Administer and govern
People, administration and policy to guide the use of the platform.
- Claramente
- Explain what happened
Provenance, auditing and a clear trail of decisions and artifacts.
The same framework for working together.
- Identity
- Who participates and takes on each responsibility.
- Permissions
- What they can access and what they can do.
- Stable references
- Which source, file or version is used.
- Operational contracts
- How work is requested, executed and returned.
FutureCreate / Professional creation
Conversation opens up the work.
The team gives it shape.
Creating also means editing, checking sources, receiving comments and finishing a deliverable another person can use and continue.
iMunaCreator,
in FutureCreate.
FutureCreate integrates iMunaCreator for professional creation, editing and review of deliverables. Specialized agents work across applications, supporting people throughout the task.
The vision includes generation from Inteligentemente, alongside editing tools and the team’s judgment.
Explore iMunaCreatorOne space for many ways to create.
13 applications- Photo
- Raw
- Vector
- Video
- Motion
- Audio
- Layout
- Docs
- Sheets
- Slides
- CAD
- Forge
From source material to the reviewed version: files, decisions and their references accompany the creation lifecycle.
Learn by doing.
Create to demonstrate it.
Personalized content for each student, practice with professional tools and feedback to develop greater autonomy. The work and its versions provide evidence of learning.
05 / Adopting a capability
Find a useful case.
Turn it into a practice.
Software and infrastructure become capability when the team knows what to use them for and how to review the outcome. Support is part of that journey.
Start with a concrete need.
Choose work that matters, understand its sources and agree on what outcome would be useful. The people responsible define the criteria and boundaries.
Connect capability and process.
Configure resources, tools, permissions and references. Prepare the workflow, its deliverables and the points for human review.
Learn, review and adjust.
Practice with the team, review versions and evidence, document what works and adjust the next step. FutureLearn can support training and practice with FutureCreate.
Explore in greater depth
Look at the work
in more detail.
The stories above explain the journey. These resources let you explore the document lifecycle and other situations each team can adapt to its context.
How the operation and its document move forwardSources, versions, review and approval +
Two connected lanes. Preparation produces draft v1; review produces comments and v2. Corrections return the work to preparation and review. Approval is tied to version v2 and allows that version to be delivered with its record.
OperationPeople, decisions and executionView the document
- 01
Request
Express the assignment.
FutureChat↳ Sources - 02
Owner
Define the scope and who decides.
People · FutureControl↳ Assignment sources - 03
Preparation
Coordinate and prepare the work.
FutureOps · FutureCreateView draft v1 ↓ - 04
Review
Comment and correct.
People · FutureCreateView comments and v2 ↓ - 05
Approval
Approve version v2.
Human ownerView the approved version ↓ - 06
Delivery
Deliver what was approved.
FutureOps↳ Record
DocumentSources, versions and evidenceBack to the operation
Sources
Authoritative originals.
FutureDiskDraft v1
A first version, preserved.
FutureCreate · FutureDiskComments
Review observations.
People · FutureCreateVersion v2
Corrections incorporated.
FutureCreate · FutureDiskApproved version
Approval references v2.
FutureDisk · Claramentecommercial-proposal · v2Record
Who, which version and what happened.
Claramente
Corrections return the work to preparation and review. If an approved version changes, it needs a new approval.
The assignment and the document move forward together: preparing a draft is not the same as approving it.
One approval, one version. The decision is tied to commercial-proposal v2. A new version requires a new approval.
Sources first. FutureMemory retrieves permitted context and controls its reuse. Memory does not replace sources or the authoritative record.
Permissions in each service. FutureOps coordinates the work. Each resource enforces its permissions; FutureControl brings together policies and administration.
Other situations to discover with the team32 grouped journeys to explore and adapt +
Futuramente in real-world situations
More situations to explore.
Ideas to discover with each team. The stories above show how the complete journey connects; these tasks open up discussion of other needs, sources and review criteria.
People retain decision-making authority.The team reviews the work and authorizes commitments, deliveries, purchases, access, and publication. Approval identifies the agreed version and action.
Internal requests
- Trigger
- Another department makes a request with incomplete information or priorities that still need to be agreed.
- Work and review
- Clarify the request, gather background information, and propose a scope, owner, and deadline. The requesting department validates the priority, and the person receiving the work accepts the commitment.
- Documents and outcome
- Request brief, sources, and task plan: an agreed assignment the team can track.
Commitments and deadlines
- Trigger
- An agreement, meeting minutes, or a contract sets out commitments with approaching deadlines.
- Work and review
- Check dates and conditions against their sources, prepare follow-up, and flag exceptions. The people responsible confirm progress and approve any changes to commitments.
- Documents and outcome
- Deadline calendar and follow-up minutes, with evidence of the current status and notices prepared for review.
Blockers and dependencies
- Trigger
- A deliverable is waiting on a decision, another task, or capacity that is unavailable.
- Work and review
- Map dependencies, team workload, and alternatives. Coordinate a review with the affected departments; their leads agree on the priority and authorize replanning.
- Documents and outcome
- Dependency map and revised plan, with blockers, owners, and dates validated by the team.
Handoffs between departments
- Trigger
- Work moves from sales to operations, from one shift to another, or to a different team.
- Work and review
- Gather decisions, files, and outstanding items; identify missing information and prepare the handoff. The receiving team reviews the scope and confirms which responsibilities it accepts.
- Documents and outcome
- Handoff package and receiving checklist, with sources, outstanding items, and acceptance from both parties.
Acceptance and rework
- Trigger
- Work is delivered and feedback or unresolved acceptance criteria emerge.
- Work and review
- Link each comment to the relevant version and criterion; coordinate corrections and another review. The person responsible approves the version being accepted.
- Documents and outcome
- Feedback matrix, corrected version, and acceptance record; closure refers to the approved file.
From opportunity to proposal
- Trigger
- A sales inquiry arrives with needs, background information, and questions that remain open.
- Work and review
- Organize the context, prepare questions, and coordinate the scope, estimate, and proposal. The sales team reviews assumptions, prices, and commitments before approving an offer.
- Documents and outcome
- Opportunity brief, versioned proposal, and validated budget, ready for authorized delivery.
From quote to order
- Trigger
- A customer accepts a quote, and preparations are needed to start the order.
- Work and review
- Check products, quantities, terms, and validity; coordinate sales and operations reviews. A person confirms the order and authorizes the commitment before it is recorded.
- Documents and outcome
- Identified quote, draft order, and terms checklist, with any differences resolved by the team.
Getting started with a customer
- Trigger
- A commercial relationship is confirmed, and several departments need to get the service underway.
- Work and review
- Gather the agreed scope, contacts, and materials; prepare onboarding tasks and kickoff meetings. Each owner validates their commitments and approves the necessary communications or access.
- Documents and outcome
- Onboarding plan, kickoff agenda, and customer folder, with confirmed next steps.
Customer complaints and follow-up
- Trigger
- A customer reports a problem with a service, product, or delivery.
- Work and review
- Consolidate background information, evidence, and owners; coordinate alternatives and draft a response. The responsible team approves any remedy, compensation, or communication to the customer.
- Documents and outcome
- Complaint file, timeline, and reviewed response, with the agreement and its follow-up tasks.
Renewals
- Trigger
- A service or agreement is approaching its expiry date and needs to be reviewed.
- Work and review
- Check the history, needs, and terms; prepare scenarios and questions for negotiation. A person decides on the proposal and authorizes any renewal or new commitment.
- Documents and outcome
- Renewal brief, comparison of options, and draft terms for an informed negotiation.
Supplier onboarding
- Trigger
- A department proposes working with a supplier that is not yet on the register.
- Work and review
- Request and organize the required background information, flag missing items, and coordinate internal reviews. The responsible departments validate the data and authorize registration.
- Documents and outcome
- Supplier folder and onboarding checklist, with comments, owners, and a recorded decision.
Coordinated purchasing
- Trigger
- The team needs to purchase supplies, a service, or equipment.
- Work and review
- Gather quotes, terms, and evaluation criteria; prepare a comparison and coordinate inquiries. Authorized people choose an option and approve the purchase before an order is issued.
- Documents and outcome
- Offer comparison, purchase request, and approval file, with the sources for each option.
Invoice, order, and receipt
- Trigger
- An invoice does not match the order or what was received.
- Work and review
- Check quantities, amounts, and supporting documents; coordinate the review between purchasing, receiving, and administration. The responsible department validates the resolution before any payment or adjustment.
- Documents and outcome
- Reconciliation table and discrepancy file, with supporting documents and a reviewed resolution.
Expenses and expense reports
- Trigger
- A team needs to report expenses for a trip, an activity, or a period.
- Work and review
- Organize receipts, classify expenses, and flag missing items or exceptions to internal policy. The person responsible reviews the expense report and authorizes any reimbursement.
- Documents and outcome
- Expense spreadsheet with references to receipts, comments, and an identified approval.
Proposed replenishment
- Trigger
- Stock records show a need for replenishment based on expected consumption.
- Work and review
- Check stock levels, movements, and demand; review the dates of the data and compare supply alternatives. The team validates quantities and authorizes any purchase or stock movement.
- Documents and outcome
- Replenishment proposal and calculation spreadsheet, with assumptions, sources, and reviewed quantities.
Asset maintenance
- Trigger
- An asset needs a scheduled inspection or has a reported fault.
- Work and review
- Gather background information, record symptoms, and coordinate availability, materials, and owners. A qualified person reviews the plan and authorizes the maintenance work and its closure.
- Documents and outcome
- Asset record, proposed work order, and maintenance checklist, with evidence reviewed by the person responsible.
Current documents
- Trigger
- Different versions of a procedure are circulating, or references to its sources are missing.
- Work and review
- Identify originals and owners, compare changes, and prepare a consolidated version with permitted access. The document maintainer reviews and approves which version remains current.
- Documents and outcome
- Document index, comparison of changes, and approved version, with stable references to the originals.
Preparing tender submissions
- Trigger
- Tender specifications arrive with conditions, documentation requirements, and a submission date.
- Work and review
- Break down requirements, assign preparation work, and link evidence to each item. The people responsible review the responses and authorize the final version and its submission.
- Documents and outcome
- Requirements matrix, list of outstanding items, and versioned submission file, prepared for the team's decision.
Market research with sources
- Trigger
- A product or sales decision requires an understanding of a market or a comparison of alternatives.
- Work and review
- Gather dated sources, compare findings, and distinguish evidence, assumptions, and open questions. The team reviews the conclusions before using them to make decisions.
- Documents and outcome
- Research report and comparison table, with links to sources and explicit limits to the evidence.
Learning by doing
- Trigger
- Each student needs to progress from different prior knowledge, goals, and difficulties.
- Work and review
- Personalize materials and exercises; propose a practice activity in FutureCreate and review the work with the educator. Feedback guides the next step, and the person responsible validates the learning path.
- Documents and outcome
- Personalized guide, practice artifact, and feedback: evidence of learning to adjust the path.
Suggested support responses
- Trigger
- A support inquiry arrives that can be resolved using permitted documentation and background information.
- Work and review
- Connect the question to current sources, prepare a response, and indicate when to escalate. The support person checks the proposal and approves the message and any action.
- Documents and outcome
- Draft response with references and a case record, ready for review and authorized delivery.
Budgets and scenarios
- Trigger
- A budget needs to compare costs, quantities, or alternatives under different conditions.
- Work and review
- Structure a spreadsheet, prepare scenarios, and review formulas, sources, and sensitivity. The person responsible validates the assumptions and decides which option and budget to approve.
- Documents and outcome
- Editable scenario spreadsheet and decision note, with calculations that can be reviewed and identified assumptions.
Reports for decision-making
- Trigger
- A period ends, or a meeting requires an explanation of results and outstanding items.
- Work and review
- Consolidate data the team is allowed to use, check figures, and develop the narrative in FutureCreate spreadsheets and slides. The team reviews the results and approves the version to be shared.
- Documents and outcome
- Report with sources, an editable spreadsheet, and an editable presentation, with comments and an identified final version.
Multiformat campaigns
- Trigger
- A campaign needs to adapt a message for different audiences and formats.
- Work and review
- Coordinate the brief, prepare copy, images, and layouts in FutureCreate, and organize feedback. The person responsible validates the brand, content, and each asset before authorizing publication.
- Documents and outcome
- Brief, editable originals, and proposed calendar, with approved campaign versions.
Catalogs and photography
- Trigger
- Products are added, or their data and presentation materials change.
- Work and review
- Check specifications, review photographs, and compose product sheets and pages in FutureCreate. The team validates data, images, and terms before authorizing distribution.
- Documents and outcome
- Edited photographs, product sheets, and an editable catalog, with product information sources and an approved version.
Publishing and translation
- Trigger
- A document needs to be edited, translated, or prepared for another audience.
- Work and review
- Work from the original, maintain terminology and references, and coordinate reviews of content, language, and design. The people responsible approve each version before publication.
- Documents and outcome
- Edited original, translation, and layout in FutureCreate, together with a delivery PDF and change log.
Podcasts and video
- Trigger
- A story or educational content requires an audiovisual production.
- Work and review
- Coordinate the script, sources, storyboard, and audio and video editing in FutureCreate. The team comments on versions, and the person responsible approves the cut and its publication.
- Documents and outcome
- Script, editable session or project, transcript, and approved master, with sources for the material.
Preparing a release
- Trigger
- A new version is being prepared to reach its users.
- Work and review
- Gather tests, dependencies, risks, and outstanding items; prepare the rollback plan and coordinate the review. The person responsible decides whether to release and authorizes any deployment.
- Documents and outcome
- Readiness checklist, QA evidence, and release and rollback plan, with an identified decision.
Agents and runs
- Trigger
- A run is blocked, fails, requests approval, or reaches a cost limit.
- Work and review
- Review steps, permissions, results, and resource usage; prepare an alternative or a retry with FutureOps. The person responsible authorizes pending actions, new limits, and retries that require authorization.
- Documents and outcome
- Run summary, incident log, and revised plan, with costs, decisions, and related evidence.
Granting and revoking access
- Trigger
- A person joins, changes roles, or stops participating in a team.
- Work and review
- Check the role and resources, prepare requests, and coordinate with the administrators of each system. Authorized people approve granting or revoking access and verify the result.
- Documents and outcome
- Access matrix, requests, and completion checklist, with approvals and verification evidence.
Software requirements and QA
- Trigger
- User feedback or a product request requires a change to be defined.
- Work and review
- Organize requirements and acceptance criteria, prepare test cases, and link findings to their evidence. Product and development teams review the definition and accept the results.
- Documents and outcome
- Specification, test plan, and findings log, with acceptance decisions reviewed by the team.
Interface prototypes
- Trigger
- A new flow needs exploration of how people would understand and complete a task.
- Work and review
- Prepare alternatives and a prototype in FutureCreate, coordinate tests, and review interaction, content, and accessibility. The team decides which proposal moves into development.
- Documents and outcome
- Wireframes, prototype, and a summary of observations, with a design decision and agreed changes.
More to explore
The family is also
taking shape here.
Discover the family’s initiatives and explore their current pages in greater depth.