EmailHigh
Confirm revised delivery schedule
Customer asks whether the staged delivery can begin Friday.
Unassigned8 min ago
Unified Work Interface / Product 001
Product Development Concept
One Board for Work Across Every Tool.
Fonte means “source” in Italian. Fonte UI is a proposed operating layer designed to become the source interface for messages, tasks, decisions, and agent actions across everyday work.
Fonte Means “Source” in ItalianEmail / WhatsApp / Teams
Operational View / IllustrativeConcept Model
Email
WhatsApp
Teams
One Work Queue
Review, assign, discuss, approve, respond, automate, and complete without reconstructing the work in another tool.
ReviewWith Context
AssignClear Owner
RespondAt Source
02 / 14
The Board
Work From Different Channels Becomes One Queue.
The Kanban board gives each request a visible state, owner, next action, and history. The example below demonstrates the product model; it is not a live production workspace.
Communication Operations
Illustrative Product Model / Sample Data
07 Items03 Sources01 Approval
Incoming
02WhatsAppNormal
Supplier stock update
Three materials are ready; one needs a replacement date.
Operations14 min ago
Review
01TeamsApproval
Approve customer exception
Commercial terms and the original request are attached.
MayaDue today
In Progress
02EmailActive
Prepare response with options
Draft two workable timelines from the project history.
ArjunEdited 6 min ago
AgentReview
Summarise the account history
AI-assisted summary is ready for a person to verify.
Review QueueHuman check required
Waiting
01WhatsAppExternal
Confirm replacement date
Follow-up remains linked to the supplier conversation.
NehaWaiting 2 hours
Complete
01TeamsSent
Share approved delivery plan
Decision, response, and activity history stay on the card.
ArjunClosed 11:42
03 / 14
The Operational Problem
The Work Is Connected. The Interfaces Are Not.
One request can be copied into a task manager, discussed in chat, supported by a document, and remembered as a follow-up. Every handoff asks someone to rebuild the context and decide who owns the next step.
01
Email Thread
02
WhatsApp Chat
03
Teams Request
04
Task Board
05
Document
06
Calendar Reminder
07
Someone’s Memory
The cost is the reconstruction between them.
04 / 14
Core Proposition
Keep the Work on the Board.
Fonte UI is intended to turn incoming activity into an operational object. The card carries enough context to assign, discuss, approve, respond, automate, and complete the work without losing its source.
Work Card / 0247
Original Request
Source and Participants
Files and Decisions
Discussion and Ownership
Actions and Responses
Automation History
Current State
01Channel Activity
02Work Card
03Assignment
04Action
05Response
06Completion
05 / 14
Initial Deployment / Communication Operations
Start With the Messages That Become Work.
The first planned workflow combines email, WhatsApp, and Microsoft Teams in one queue. It is a focused implementation wedge for testing whether teams can review, organise, assign, and respond from a shared operating surface.
Planned Scope / V1
Three Inputs.
One Queue.
The first version is an operational layer above existing platforms. It focuses on a complete, testable communication workflow before broader expansion.
01
Connect email, WhatsApp, and Microsoft Teams.
02
Convert selected communications into board items.
03
Preserve the source, participants, and conversation context.
04
Assign ownership, priority, and next action.
05
Reply through the appropriate source connector.
06
Track pending responses and follow-ups.
07
Share work with other users.
08
Retain a useful activity history.
06 / 14
Workflow Demonstration
From Customer Email to Approved Response.
The workflow keeps automation bounded. An agent may prepare a summary or draft, while a human remains responsible for reviewing the context and approving what is sent.
- 01
Message Received
A customer sends an email with a request.
- 02
Card Created
Fonte UI creates or updates the work item.
- 03
Context Prepared
The message is summarised and categorised.
- 04
Owner Assigned
A user sets ownership, priority, and next action.
- 05
Team Review
A teammate checks the source, files, and history.
- 06
Response Drafted
A person or approved agent prepares a response.
- 07
Human Approval
A human verifies the response before it leaves.
- 08
Reply Sent
The original email connector sends the response.
- 09
State Updated
The card moves forward with a recorded outcome.
07 / 14
System Position
A Shared Surface Above Existing Software.
Fonte UI is intended to connect distributed systems while giving users one place to manage the resulting work. The initial connectors establish the workflow; future and custom connectors extend it around real operating needs.
Initial
Initial
Initial
Microsoft Teams
Fonte UI
Shared Work Surface
Future
Documents
Future
Calendars
Custom
Databases
Custom
Business Tools
Future
AI Agents
Extensible
More Connectors
08 / 14
Extension Architecture
Add the Skills the Workflow Needs.
The platform vision is extensible rather than defined by a fixed integration list. Each useful workflow still carries engineering work: credentials, permissions, testing, observability, failure handling, and connector maintenance.
01
Connectors
Read from and act through approved external applications.
02
Skills
Handle bounded tasks such as extraction, drafting, classification, retrieval, and reporting.
03
Agents
Coordinate multi-step work with approved tools, context, and human checkpoints.
04
Rules
Control routing, credentials, permissions, approvals, and escalation.
05
Custom Workflows
Shape cards, states, triggers, and actions around one organisation's work.
Generality is earned connector by connector and workflow by workflow. That implementation cost is part of the product strategy: build the capabilities users repeatedly need, then generalise the infrastructure supported by those real deployments.
09 / 14
Product Strategy
Build the General Platform Through Specific Workflows.
The broader interface becomes credible by solving focused operational problems first. The first measure of progress is whether users can keep the work, its actions, and its response history on the board.
- 01
Choose one recurring, commercially useful workflow.
Stage 1 - 02
Build only the connectors and actions needed for that workflow.
Stage 2 - 03
Test whether users keep the work and its context on the board.
Stage 3 - 04
Improve permissions, approvals, actions, and collaboration.
Stage 4 - 05
Add adjacent workflows when the shared infrastructure proves reusable.
Stage 5
10 / 14
Market and User Fit
For Teams Where Communication Already Runs the Work.
The strongest early fit is likely to be teams that receive meaningful requests across several channels and still depend on manual copying, individual memory, or one person to keep the operation moving.
Small Businesses
Communication spread across business and personal accounts.
Agencies
Client decisions divided between email, chat, documents, and task boards.
Founder-Led Teams
One person still routes most requests, decisions, and follow-ups.
Operations Teams
Requests arrive through several channels without shared ownership.
Distributed Teams
Communication and task-management systems hold different parts of the work.
Custom-Workflow Teams
The operation needs a tailored layer without replacing its complete software stack.
11 / 14
Current Stage / Product Development
Seeking the Support to Build the First Complete Workflow.
Brownsmith Dynamics is seeking funding, strategic support, and design partners to turn the concept into a validated implementation for communication operations.
01
Product and Interaction Design
02
Email, WhatsApp, and Teams Connectors
03
Authentication and Permissions
04
Shared Workspaces and Collaboration
05
Credential Management
06
Message Normalisation
07
Kanban Workflow Infrastructure
08
Human Approval Systems
09
Agent and Skill Runtime
10
Audit History and Observability
11
Security Review
12
Pilot Deployment and User Research
12 / 14
Why Brownsmith Dynamics
Built Around Real Business Workflows.
Fonte UI extends Brownsmith Dynamics’ existing focus on practical AI, workflow automation, internal tools, and custom software. The product starts from how a team handles work today and adds a focused operating layer one deployment at a time.
Applied AIWorkflow AutomationInternal ToolsCustom SoftwareSmall-Business SystemsIncremental Deployment
13 / 14
Investor, Operator, and Design Partner Conversations
Help Build the First Workflow.
If you invest in operational software, manage fragmented communication workflows, or want to explore a pilot, Brownsmith Dynamics would like to hear how the first implementation should be tested.
Fonte UI
One source interface for work across distributed systems.