Iris Coordination
Your entry point. Iris takes the request, proposes which department prepares it and lets you know when there is something to review.
Lynx Virtual Office · by Lynx.studios
An AI office set up for your company.
Iris coordinates, the departments we define with you prepare the work, and you review every result before using it. It all happens in a visual office where you can see who is doing what.
Private deployment for each company. Scope, tools and providers are agreed before we start.
Product in active development. The demo distinguishes what is available, what needs a pilot, and what requires implementation.
- Iris, the coordinator who takes your request.
- Meetings, where work is assigned and reviewed.
- Departments with configurable profiles.
Use cases
Three illustrative walkthroughs of everyday office work.
They are examples that show how a request moves through the office. In the demo they run on sample data; using them with your documents or tools requires setting them up and testing them in your deployment.
Illustrative walkthrough with sample data
In your deployment set up and tested before use
-
Preparing a proposal
“Draft a proposal for this client based on what we discussed yesterday.”
Iris splits the request: one profile gathers the client information, another drafts the structure and tone, and the draft comes back to you for review. You decide what gets sent and when.
IllustrativeRequest, assignment and draft with sample data.In your deploymentUsing your templates and rates means loading them and validating drafts with your team. -
Summarising a project
“Where is the project at, and what is left to close it?”
The office pulls the project’s tasks, activity and notes into a summary: what is done, what is pending and what is blocked. It works as a starting point for a meeting or an internal report.
IllustrativeSummary of a sample project.In your deploymentReading your project tool is only possible if the connection is agreed and verified. -
Answering from your documentation
“Draft a reply to this enquiry using only our terms.”
The draft is prepared from the documents you authorise: terms, catalogues or procedures. Someone on your team checks the reply before it is sent.
IllustrativeReply based on sample documentation.In your deploymentYour documentation is reviewed and loaded into your office, and replies are tested before use.
How a request works
From goal to reviewed result, in four steps.
Goal
You tell Iris what you need, in your own words. Iris turns it into a task with an expected deliverable.
Context
The task draws on the company resources you have allowed: documents, guidelines and projects.
Team
Iris assigns the work to the right department. The office shows who has it and what state it is in.
Review
The result arrives as a draft. You approve it, correct it or ask for another version before using it.
Product
An office you can read at a glance.
The visual office replaces endless lists: every department has its place, and every request has its path.
Lynx Dot for Windows. An optional add-on for leaving requests with Iris from the desktop. Whether it is included depends on availability and on the scope agreed for each deployment.
Departments Configurable
We define with you the departments and profiles your company needs, with their instructions and way of working.
- Sales
- Customer service
- Operations
- Administration
- Whatever your company needs
Context Per company
Each office is set up with its company’s resources: documents, guidelines, data and prepared tools. How data and access are separated is defined in each deployment’s architecture.
Tracking Tasks and activity
Tasks, projects and activity are logged. You can see what was asked, who prepared it and what is waiting for review.
Deployment
Deployed with you, step by step.
It is not an account you open and configure on your own. We prepare your office, test it with your team and adjust it during start-up.
Diagnosis
We look at which tasks your team repeats, which documents it works with and where time is lost. We choose where to start.
Setup
We create your departments and profiles, load the authorised resources and prepare the agreed tools.
Testing
We test each case with real work from your company and review the results with you before day-to-day use.
Support
During start-up we adjust instructions and guidelines based on what your team finds when using it.
Agreed capacity
We set out in writing which cases are active, with which tools and at what volume of work. Expanding it is your decision.
Architecture, permissions and providers are agreed for each deployment.
AI models, connectors and any action on other tools depend on what your company needs and authorises. We explain what is used and why before it is switched on.
Data and control
You decide what goes into your office.
We explain in concrete terms how your company’s information is handled, including what depends on third parties.
No system is infallible. That is why every result goes through a person before use, and we document the limits of each configuration.
- Architecture per deployment
- How data, access and environments are separated is decided and documented for each deployment. The client experience reuses the design of the internal Lynx.studios office, not its data or credentials.
- Permissions you define
- You decide which documents and tools the office can use, and who on your team can access each part.
- Review before action
- Results arrive as drafts. Actions on other tools are only switched on if they are agreed and verified in your deployment.
- Agreed providers
- Third-party AI services may be involved in generating text. We tell you which ones, what information they receive and their terms, and they are agreed before we start.
- Logged activity
- Requests, tasks and results are logged in your office, so you know what was asked and what was delivered.
FAQ
Common questions before a demo.
What will I see in the demo?
The visual office, how Iris receives and assigns a request, and the illustrative walkthroughs on this page with sample data. Then we talk about which of your company’s tasks might fit.
How much does it cost?
Each deployment has its own budget, based on scope: cases, tools to prepare and support. After the diagnosis you receive a written proposal. There are no self-service plans or payments on the website. More detail in scope and budget.
Does it work for my industry?
We start from processes, not industries. If your process needs something specific or is subject to particular regulation, we assess it in the diagnosis and tell you clearly whether we can take it on.
Does it connect to the tools we already use?
Some connections can be prepared, but each one is agreed, configured and verified in your deployment. A tool appearing in a catalogue does not mean it is connected.
Does it work on its own, unsupervised?
No. The office prepares drafts and someone on your team reviews them before they are used or sent.
What about our data?
Architecture, permissions and providers are agreed in your deployment, and the office only uses the resources you authorise. We explain which providers are involved and what information they receive. See also the privacy policy.
What happened to the web and SEO services?
The agency-stage pages are still published as resources: web design, local SEO and automation. Lynx.studios’ main offer is now the private office.
Request a demo
We’ll show you the office with a sample walkthrough.
- A guided walkthrough of the office with sample data.
- We look at which tasks might fit and which would not, with no commitment.
- If we go ahead, we send you a written scope proposal.