Seed round · confidential

From conversation to completion.

One workspace for conversations, meetings, projects, clients, files and AI — so the work a team talks about is the work that actually gets done.

Teams talk in one tool and work in another.

Conferencing, chat and project software each solved their own slice. The seams between them are where the work is lost — and the seams are what nobody owns.

Three things changed at once.

One shared object model — not three products in one shell.

Every message, meeting, task, file, decision and client record links to the others by design. That single decision is what makes the product feel unified — and what makes it hard to copy by bolting products together.

Nine surfaces. One identity. One permission model.

Conversation to action

Why it matters Commitments stop being verbal. Every other tool asks a human to notice a promise, switch apps and retype it. Most of the time they don't. We make the promise the task, and keep the original sentence as evidence.

The persistent meeting workspace

A meeting is an object with a lifecycle, not an event that disappears — one workspace holds the whole arc.

Before Context arrives with the invite

Agenda and owners Pre-read files from the project Participant roles Project and client links Security posture set by policy

During Everything is captured in place

Live transcript and captions Screen share and whiteboard Chat, polls, Q&A, reactions Collaborative notes Bookmarked moments

After — where the value is The meeting keeps working

AI summary and decisions Action items with owners and dates Tasks confirmed onto the board Follow-up scheduled from the same place Permanently searchable by timestamp

External collaboration as a growth engine

A client opens an invitation and lands in exactly the shared space — no tenant switching, no licence to buy.

Internal memberExternal partnerClientVendorGuest · auto-expiresViewer

The commercial logic Keep client access cheap enough to be viral. Every client space puts our product in front of another organization, doing real work, at their vendor's expense. Licensing friction on guests is the single biggest thing incumbents get wrong — and the cheapest advantage for us to take.

One AI layer over all authorized work

Because chat, meetings, files and tasks share one model, the assistant sees the whole picture — and never more of it than the person asking is allowed to see.

Governance requirement The AI has exactly your permissions. Never more. It cannot summarize, retrieve or act on content you could not open yourself. Retrieval is tenant- and ACL-filtered server-side, every answer cites its sources, and admins can disable models or features per workspace.

Answers that link to the evidence

Semantic and keyword search over one index of messages, meetings, files and tasks. The answer is not a list of links — it is a claim with a citation you can open.

Why competitors can't answer this A chat tool can only search chat. A meeting tool can only search its own recordings. The answer above needs all four object types and one permission model — which is exactly what our data model was built for.

Knowledge continuity Six months later, this still works — and the value compounds with every meeting recorded and every task linked.

We do not need to win video or chat. We need the columns nobody owns.

Start where client work and meetings collide.

Earn one vertical properly before touching breadth.

Per-seat subscription, four tiers

Packaging shown; price points to be validated with design partners and competitive testing before launch.

Seats are the floor. Usage is the ceiling.

Separate services. One tenant and permission context.

Buy the hard media infrastructure. Build the workflow.

Video reliability is a solved commodity for a team our size, and a two-year distraction if we treat it as a differentiator. Our differentiator sits above the media plane.

Designed into the data model, not bolted on later.

Every business object carries tenant and workspace identifiers. Authorization is enforced server-side — including for search and AI retrieval.

Prove the unified workflow before expanding breadth.

What must be excellent — and what can wait.

A focused team of 12–16 through Phase 2.

Built and operated by Tanco Tech Consulting — an IT consulting and software firm with delivery experience in web, mobile, cloud, AI and digital health systems.

Two metrics decide whether the thesis is true.

Percentage of meetings that produce tasks, and percentage of tasks linked to a message or meeting. Everything else is supporting evidence.

The biggest risk is us building too much.

Twelve gates before public launch.

Fund Phases 0 through 2 — the differentiated product.

Allocation shown as a percentage of round; set the raise amount against your own runway model. Roughly 9–12 months to a Phase 2 product with paying design partners.

Not whether we have every button. Whether a team can go from conversation to decision to execution without losing context.

Worqex — talk, meet, work. All in one place. info@tancotechconsulting.com
+1 (972) 836-8111 · Plano, TX