Project / build · In market
SiteSupply
A B2B construction procurement marketplace built around comparable quotes, for buyers and suppliers across Canada and the United States.
The build portfolio
Ideas are useful.
What we build with them matters.
Software, project builds, operator publications, and community work. Different expressions of the same engineering discipline.
01 / Owned software
Software with a job to do.
Owned software, built around real operating workflows.
sivanta.CONVERSATION → COMMERCE
WhatsAppTelegramWeb chat
- 01One conversation modelChannel adapters normalize incoming messages.
- 02The right skill. Clear boundaries.Registered skills run through policy and approval.
- 03Checkout, with a human route.Complete the transaction or escalate for judgment.
Skills → Policy → CheckoutHuman handoff ↗
Conceptual architecture · not a customer interface.
Owned product · Active
Sivanta — conversation-led commerce
Multi-tenant commerce automation for customer-facing teams: governed conversation flows across WhatsApp, Telegram and the web, with a skill registry, a policy layer, checkout and human handoff.
Explore the product’s capabilities, plans and operating boundaries—or see how it connects to the wider Tayoca estate.
02 / Ventures & builds
Market work in progress.
Builds Tayoca is helping bring to market. Where a relationship or ownership position is not ours to assert publicly, the classification stays neutral on purpose.
What counts as evidence here
No invented screenshots, clients or results.
Portfolio entries appear only where a canonical source exists in the repository or on this site. Items that remain private, unverified or disclosure-pending are recorded in the company inventory rather than published — and this page grows as their evidence does.
Ownership and naming questions are resolved deliberately, not by inference.
Read the disclosure rules →03 / Publish & teach
Knowledge we write down and ship.
Editorial and publications are a first-class output at Tayoca, not marketing filler. Both are gated by the same evidence and approval rules as everything else.
Publication · Weekly
The Operator Brief
An eight-section briefing for leaders responsible for cloud, platforms, reliability, AI infrastructure and technology economics. Repository activity may inform the editorial desk, but nothing is published as a raw commit digest, and every issue is approved by a human before it ships.
Publications · 8 titles
Operator Playbooks
Books, workbooks, lab packs and checklists for teams that would rather execute the work themselves. Each title has a defined buyer, problem, deliverable and evidence boundary in the Tayoca product ecosystem.
04 / Community
Work we give away on purpose.
The Free Website Initiative is a research-first programme for local Ontario small businesses. It is a community initiative, not a lead funnel with a sales obligation attached.
Community initiative · Open intake
Free Website Initiative — Round 01
Ten free website core builds for local small businesses across Shelburne, Orangeville, Alliston, Dufferin County, Simcoe County and nearby communities. The core build is provided at no charge for selected businesses and there is no requirement to buy hosting, maintenance, a CMS, SEO or another service from Tayoca.
05 / Internal systems
The operating system behind the company.
These are internal capabilities. They are described for context and are deliberately not linked as public showcases.
Internal system · Access-gated
Tayoca Control Center
The internal console used to publish and govern this site: structured website content, global site settings, navigation and footer configuration, media, revision history and restore, plus automation and workflow operations.
Access is restricted to authenticated operators. It is described here because it explains how Tayoca works, not as a product for sale.
Internal system · Orchestration
Automation and intelligence fabric
Workflow orchestration connects website forms, the source repository, editorial approval, community intake, revenue operations, reviews and project intelligence, with recovery and audit behaviour defined in policy.
Raw evidence stays authoritative in its originating system; automation moves and records it, it does not become the truth store.
06 / Classification
How Tayoca decides what may appear here.
Existence, ownership confidence, disclosure permission and publication status are tracked separately. Something can be real and still be absent from this page.
Existence
Is there verifiable evidence the project exists — source, a live surface, or a canonical internal record?
Nature & relationship
What kind of thing is it, and what is Tayoca's actual relationship to it: owned, built, advised, contributed, internal?
Disclosure permission
Third-party, client and community work needs consent. Without it the item stays out of the public IA regardless of merit.
Public classification
Only then is a public label chosen: owned product, venture build, publication, community programme or internal system.
Publication status
Published, staged, or recorded-not-published. The distinction is visible on the page, not hidden in a spreadsheet.
Recorded, not published
Some real Tayoca-adjacent projects are held in the internal company inventory while ownership or disclosure is confirmed. Holding an item back is a deliberate classification decision — an unresolved item is never silently dropped, and never silently published either.
What could we
build together?
Start with the problem, then find the right scope.
Start an Assessment ↗