Nextora is built in the open, week by week — from a PDF engine to an operating system for the whole company: CRM, ERP, omnichannel conversations, automation and AI employees. This is the record, drawn from the product’s own commit history.
Calendar can show teammates’ calendars next to your own, live, and you decide in settings who sees yours. Administrators can open an employee’s mailbox in Email read-only; the reply box says that only the owner answers.
See teamworkHiring now works like the Workshop: describe the role in your own words, answer a few pointed questions in the language of your brief, and grant access in one step. In chat, an AI employee answers a request for advice straight away instead of asking for access first.
AI employees, explainedPaste a link and the Workshop works from a summary of that page; type @ to hand it a board, a notebook page, a form or a CRM record with its fields.
Which tool for which jobEmail connects Outlook and Microsoft 365, Gmail with an app password, or any provider over IMAP and SMTP, from a Connect a mailbox window right in Email. Mail syncs on the server into the same threads and sends the same way, so a closed laptop no longer means a stale inbox.
See conversationsThe whole interface and the built-in guide are now available in Ukrainian, picked from a language list written in each language’s own name. AI features answer in the language you work in, and tours, invitations, signing emails and signed PDFs follow it too.
A small ring beside every AI request field shows how much of this cycle’s credits is left and how much the current section has used. Open it for the renewal date, the daily average and, if the current pace will not last, the day the credits run out.
See AI teammatesStep-by-step tours walk through leads, tasks, deals, analytics, calls, bots, signing, ERP and settings, narrated if you want them to be. They all start from one place: the ? menu in the header, next to the guide.
Pipelines, stages, assignees, relations, notes, settings and shared content now check the same permissions in the database that the interface shows, and automations act with the rights of the person who owns them. Every member now has a role.
Designing accessIn e-signing, Find fields scans a document for blanks (underlines, dot leaders, “Signature:” labels, tick boxes) and AI decides what each one is, which signer it belongs to and whether the CRM already knows its value. The section was rebuilt around a document table, a builder, a send window and a typed signature.
Are e-signatures binding?Analytics opens on your own dashboards, with four ready-made ones calculated from your data: Sales, What is stuck, Leads and Team and tasks. Or describe a dashboard in words: a vague request is clarified before the build, and the build shows as a card in the grid until it is done.
See analyticsOrganisations with their own currency and chart of accounts, country packs, and full sales and purchase chains: documents created from one another, postings, reversals and a trial balance with drill-down and a lock date. Every document prints from one dialog with the amount in words, and WooCommerce and Shopify orders arrive as sales orders.
Quote to cash, step by stepA pipeline or task board can carry its own rules, built from When, If and Then chips: several conditions joined by and/or, several actions, waits in between. They run on the server, leave a trace in the record’s history, can be drafted by the Workshop and sit among your automations.
See automationThe desktop app now installs on Windows, updates itself and lives in the tray; on Windows and macOS a new window opens with Ctrl+N or ⌘N beside the active one. Sign-in goes through the browser with a one-time code, the bell arrives as system notifications in the background, and macOS gains desktop widgets.
The app now draws the screen you asked for before anything else: header widgets, the editor, phone-number flags and the assistant load when they are needed, the bell asks for a count instead of a list, and translations arrive as cached files rather than inside the code.
Lead, deal, contact, company, task and project cards share one Relations panel, where a related record is a single two-line row with its type and where the link came from. On the Gantt chart, the selected task’s links light up and the rest step back.
See the CRMA versioned REST API covers every resource, with an OpenAPI 3.1 reference, rate limits and idempotent writes. Webhooks are signed and keep a delivery log with retry and secret rotation, on every plan.
Boards, formerly Canvas, gained a full editor with alignment, keyboard shortcuts, floating arrows and live collaboration. Import from Miro, FigJam, Excalidraw, tldraw or CSV, export as PNG, PDF or a board file, share a read-only public link with an expiry, or let AI build a board from a brief.
See teamworkThrough the MCP connection Claude can now build and check reports, preview emails and pages, test a bot and work with files, and the Workshop appears as a live card in the conversation. Whatever it changes is signed as AI under the connection’s name, in chat, history and notifications.
Connecting Claude to a CRMTasks have a start date and “blocks” dependencies, drawn as soft bars with faces on a Gantt chart; draw a new task straight under the plan. A project’s tasks appear with its milestones, and Projects gains a Timeline across the whole portfolio.
See projectsThe hub became the product’s launcher: every app and tool in one panel, search across all of it, a What’s new feed with screenshots, and tips that hold still while you read. A locked app wears a lock; click it to request access.
Team gained a Structure tab: an org chart you rearrange by drag, with undo instead of confirmations, and departments as a tree with heads and sub-departments. Teams and absences sit beside it, and workload shows on people’s cards and chart nodes.
See teamworkOnboarding can be a conversation: the voice assistant reads your company’s website, asks only what it could not find, and assembles the workspace on screen as you talk. The plan changes by voice too: “add a budget field to deals”, “we don’t need projects”.
With keeping watch on, the assistant reads team chat for promises, requests and messages left unanswered, and raises each as a single suggestion on the home page or in the bell. Questions about Nextora itself are answered from the built-in guide, with screenshots and links.
See AI teammatesPlans are now self-serve from nextora.co: a 14-day trial with 2,000 AI credits, after which the workspace moves to its own server. Your account shows setup progress live, signs you into the workspace, buys extra AI credits in any amount with volume bonuses, and keeps your backups.
See pricingTeam is a section of its own: cards, search and grouping by department or role, and any avatar in the product opens that person’s profile. The profile shows their workload (in progress, overdue, closed in the last 30 days) with a way to assign them a task.
See teamworkTask spaces, notebook spaces, projects, pipelines and records can be made private, and a lock marks them wherever they appear. Each section opens with its own permission; a closed one shows No access with a Request access button, and assigning someone to a private item opens it for them.
A task can be mirrored onto another space’s board while it stays at home, or moved, and Nextora asks which you mean. Both live in the card’s ⋯ menu, moving into a project’s space makes it a project task, and dropping a card onto the middle of another nests it as a subtask.
Light or dark and your colour palette are stored in your profile, so a new device opens the way you left the last one. Several accounts can share one device: switch, add or sign out from the avatar menu, settings or the sign-in page.
A month-long pass over 184 screens: chat with full-screen threads and calls, a one-column home page and dashboards, the notebook editor with a toolbar above the keyboard, a pipeline one stage at a time, and menus that open as sheets. Builders too large for a phone open read-only with clear actions instead of breaking.
A thread counts as read when you reach its end, not when you open it. Threads, Discussions, Mentions and the bell split into New and Read, any message can be marked unread from that point down, and channel numbers count messages that need you.
See teamworkEach bot has one studio: who it is, where it works, which knowledge it may use, and a live preview where the reply streams in as it is written. A bot’s face is a two-colour orb, chosen in a click.
Before a bot goes liveThe start page is built from presets and live tiles on a bento grid (your tasks, your chat with a reply field, the day’s numbers) instead of opening on analytics.
The client hub is now a standard part of every project and looks like the product: the work plan with milestones on the overview, risks behind their own switch, files, notebook pages and task discussions, always in the light theme. The team marks which replies go to the client.
Read the guideChoices such as which branch a workflow takes, what a bot does next, or which of two similar records you meant now go to a dedicated decision model instead of a chat model. The AI: Make a decision step branches on its answer, and model settings show its status.
A form can include a Meeting booking question that shows your real free time. On submit the meeting lands in your calendar and the guest gets a confirmation with a link to reschedule, cancel or message you; a reschedule moves the calendar event even without Google.
Forms render in two layouts on one engine: one question per screen with a progress bar and keyboard answers, or everything at once. The builder splits into Questions, Design, Logic and Settings.
Getting enquiries into the CRMDescribe a campaign and the maker chooses the event that starts it; the engine then runs the sequence, pauses included, through to the exit. A catalogue of ready sequences sits beside it.
See marketingCreating a project takes three screens (a name, a brief, the tools you need) or the Workshop assembles it. Milestones take dates and names, risks take a severity, facts are edited on the overview, and the project’s pipeline board fills the screen.
From signed deal to projectPick one colour and Nextora builds a full palette for light and dark themes, checked for contrast, with an optional gradient across the whole window. Themes live in a gallery in settings and preview live in a panel docked on the right.
Chat gained group audio and video calls with incoming-call notifications; a call survives navigation and leaves a line in the channel. Telephony connects your organisation’s Twilio account and shows the CRM caller card on an incoming call, and the calls list was redesigned.
See conversationsRecord events reach the people with a role on the record, a channel shows one line until it is read, and nobody is pinged about a channel they are already watching. The notification centre gained search and a section filter, and email can arrive as one digest per period.
Changing a field’s type now converts what is in it, money, numbers and dates share one formatter, and field settings are a single menu. Views save themselves and can be personal or shared, and a deal’s outcome (won, lost, on hold) is its own field you change straight from the list.
Stages vs outcomesPersonas are AI colleagues with a role, a manager and a memory. Each works under its own permissions, reacts to events during its duty hours, remembers customers over time, reflects nightly and is reviewed weekly. Every action leaves a receipt with a 24-hour undo, and a persona that slips goes back to proposing instead of acting.
Read the guideThe chat icon in the header opens a dock on the right, so a conversation no longer costs a page. The dock steps aside on /chat itself and stops stealing Esc.
A list can be owned by several people, access is granted by name, and renaming works from the quick view, the card menu and the list header.
Colleagues appear in global search with their face and a way into a direct message. Board filters now live in the address, so a narrowed board is a link you can send.
The journal and payment flows were rebuilt around atomic finance commands, and production is recorded from frozen material requirements in one transaction — no half-posted documents.
See the ERP contourDescribe an automation, a campaign, a form or a pipeline in a sentence and it is assembled step by named step, on the server, with attachments that actually work — paperclip, paste and drag. One workshop replaced three separate AI modals.
Which tool for which jobProjects left the Tasks section and got their own rail, and the workspace reopens where you left it. Creating a project is one screen with one required field instead of a three-step wizard.
See projectsOne control row instead of three, a rail of slices on the left, filters that run on the server rather than trimming what was already loaded, and a card that says who removed it and how long it has left in the bin.
Pick the layout in your profile, drop sections you never use and bring them back later; empty sections collapse into a single action line.
A hidden column is visible in the plus popover and comes back from there, and every list got the light filter that tasks already had.
Trello-style column drag with a lifted overlay and a ghost slot, an always-present add tile at the bottom of a column, and its own menu on every subtask.
A sticky-note node with markdown, inline editing, resizing and colours — so the reason for a branch lives next to the branch.
See automationAnswering a customer in the Inbox now happens next to their record: a sales context rail with the deal, the history and what is open, instead of a second tab.
How the queue worksIt picks up incoming email and chat mentions on its own, so a summary is waiting rather than requested.
Integrations became plugins on one contract: each has its own page with the connection form, what it gives and where it stops, logs and diagnostics. Every plugin is checked end to end, and one that drifts out of step with the platform is flagged before customers notice.
Tabs are gone. A record is blocks — the answer in the header with aggregates and quick create, then What next, Feed and Discussion — arranged with a widget constructor you can drag.
A director turn that plans the letter, and attached pages and documents used as the ground truth for what it says, so the draft is written from your material rather than around it.
The widget system was rebuilt around add, remove and arrange, and the arrangement follows you between machines.
A Notion-style block menu on the handle, a selection toolbar with Turn into and colour, and a slash command that creates real nested sub-pages.
The website widget became a first-class Communications entity with a gallery of live previews and a kind-aware configurator, bot optional.
Getting enquiries into the CRMThe cockpit was rebuilt on the design system with an honest access model: a link plus a code, sections switched on one by one, a hero cover, a recent-activity feed, and the team notified when the client does something.
Read the guideDashboards became switchable views with working drag and humane settings, reports pin onto them as widgets, and a universal AI studio builds the widget from a description.
See analyticsEntity-level analytics with rich tables, formulas and real funnel and velocity maths, an aggregation-first query model computed on the server, and exports handled by a worker instead of the browser.
A clarifying interview, a multi-agent plan page, editable fields, roles and teams, and branding filled from your website — separate flows for the admin and for everyone who follows.
Google Ads and Meta Ads connectors with hub OAuth and token refresh, GA4 Measurement Protocol, conversion actions from workflows, and gclid captured on forms — so a closed deal can report itself back to the ad account.
See marketingInline field settings from the column header, drag to reorder with the whole column moving, and a real-time drop preview with a full-height insertion line.
An installable app that mirrors the web version: a frameless window with an integrated title bar, multiple windows, tray, native notifications and deep links.
A standalone canvas with its own gallery, template catalogue and builder route — plus record nodes bound to real entities, so a board can carry the work rather than describe it.
Nextora speaks MCP: a remote server over the CRM API, an OAuth 2.1 server so the connector can be added from the web, tool categories with per-domain endpoints, and a reads foundation with projection, sorting, soft-delete and restore.
/inbox became the canonical queue on a single source of truth, with widget conversations merged in, so a customer who wrote on the site and then on Telegram is one thread.
Read the guideEmail, @mentions, bot dialogues and fresh leads land in one triage queue you can clear to zero — with an owner on every conversation and a tab for the ones nobody owns.
See communicationE-signing with email invites and shareable links, inline signer editing, a faithful signed-PDF export with the signatures baked in, and reusable signing templates in their own folder.
Multi-assignee became a single source of truth across leads, deals, contacts, companies and tasks — in the create modals, the detail panels and the pickers.
A rebuilt /email inbox with team visibility and sharing, a real Sent view derived from thread direction, thread pagination and background sync.
A working toolbar, a summary band, smart views and inline-editable deal details in the side panel — the board became the place the deal is worked, not just watched.
See the CRMERP as a workspace inside the real sidebar with one entry from the CRM: a command centre, rebuilt finance and warehouse overviews, and related records one click away across ERP tables.
See the ERP contourA calm cockpit built around Flow, a clear-to-zero work queue, with an AI brief, focus mode and native task actions.
A unified catalogue, tiers, a gradient and a resolver behind every AI feature, with the legacy endpoints routed onto one run path — which is what later made model changes a settings decision rather than a release.
See AI teammatesFile uploads with drag-drop and paste, multiple attachments, and a task-creation option with field mapping and a space picker.
Read the guideA board with MyDay, an in-card timer and view tabs, plus attachments on task creation.
Three passes in one week: core coverage and reliability, then the UX — tab badge, sound, snooze, inline actions, pagination — then verified push and an email channel with tracking.
A database-backed entity registry with a runtime overlay and a service factory: model anything as a first-class record type, with CSV export from the universal toolbar.
An in-place playground, bulk actions, a quality chip and a wizard that saves as you go.
An execution canvas with a run-history panel and undo/redo, pinned execution data for testing, and trigger entity fields visible while you build.
See automationA dense week redesign with real tokens and rich cards, an enterprise event modal with relations and team invites, search, and production-grade hub OAuth with a sync queue.
The goals hub arrived with task spaces and a discussion thread on the record itself, later unified into one page driven by a metric engine over tasks, hours and leads.
A rewritten PDF renderer with signing fixes and HTTPS in production — the first piece of the document pipeline that e-signing was later built on.
A platform-wide update: the interface overhauled, the chat module redesigned around threads, saved messages and mentions, and the infrastructure underneath rebuilt.
Start a 14-day free trial and bring the workflow you want to fix.
Nextora