The request gets lost on the way
The customer asks by email, someone notes it down in chat, the developer finds out weeks later — if at all.
For software houses From the customer ticket
From the customer ticket
to the deploy, with no handoffs
You support the people who use your system and build the next release with the same team. bFocus was designed for that back-and-forth — and it is what Berni Software itself uses to run bFocus and bZapper.
- Support and projects in one place
- Widget inside your product
- GitHub linked to the tasks
The usual The three pains
The three pains
you already know
They do not come from missing tools. They come from having too many tools that never talk to each other.
The same subject, every week
Nobody can prove how many tickets that defect caused, so it never makes it into the sprint.
Nobody saw the delivery
You fix it, ship the version, and the customer keeps complaining about what has already been corrected.
How it turns out One single path,
One single path,
end to end
The same record travels through support, planning, the code and the notice to the customer. No exporting spreadsheets, no copying links between systems.
- The widget inside your product identifies the customer by the code in YOUR system
- The AI answers what is already in the knowledge base and hands over the rest with the summary written
- One click turns the ticket into a task, with the link preserved
- Repeated subjects become a single task, with the ticket count behind it
- The branch and the pull request link to the task by its key, with no plugin
- The release note goes out through the API at deploy time and lights up the badge in the customer app
- With the Monitoring add-on, your system’s error becomes a bug task before anyone opens a ticket — and once the fix ships, the team tells the people who hit it
The loop closes
When the note is published, your customers are notified and each one’s acknowledgement is recorded.
First week What you can get done
What you can get done
in five days
- 1
Day 1 — account and widget
Create the account, generate the key and paste the snippet into your system. The first tickets already arrive identified.
- 2
Day 2 — queue and SLA
Set business hours, priorities and deadlines. The queue starts sorting by real urgency.
- 3
Day 3 — knowledge base and AI
Import what you have already written, register your AI key and leave the agent in assisted mode.
- 4
Days 4 and 5 — projects
Connect GitHub, create the sprint and take the first recurring subjects into the backlog.
Use cases From the legacy system
From the legacy system
to the new app
Three common starting points in a software house, with the package that solves each one.
Your Delphi ERP, with support and AI inside the screen
Install it through Boss, create the TBFocusWidget, set the publishable key and the user, and call Init. On Delphi 10.4+ the widget runs in a WebView; from Delphi 7 onwards, on a native screen.
Desktop in Lazarus, .NET or Java
LCL package for Lazarus (Windows, Linux and macOS), WinForms and WPF on NuGet, JavaFX and Swing on Maven Central. VB6, Harbour, Visual FoxPro and PowerBuilder open through browser mode.
ERP customers and release notes on deploy
With the SDK for your language, sync customers by your own system code and publish the release note in the pipeline — it lights up the badge inside your users’ app.
First lines: boss install github.com/bernisoftware/bfocus-widget-delphi in the ERP and, on the server, npm install @bfocus/sdk or composer require bfocus/bfocus. The step-by-step for each platform is on the Native apps and Developers pages.
Details that count Things only people who
Things only people who
live this think of
Native widget in your app
iOS, Android, Flutter, React Native, .NET, Delphi, Lazarus, Java and Python — legacy systems included, through browser mode.
API and SDKs
Sync customers from your ERP, publish notes at deploy time and feed the knowledge base through the API.
One product, one brand
Every system you sell has its own logo, color, knowledge base and AI agent, under the same contract.
AI costs with no surprises
Your key, your model and a cap in reais per conversation — you know the cost per customer served.
Public task link
Show the progress to a customer without giving access to the system, and revoke it whenever you want.
Unlimited users
Put everyone in, including the people who only follow along: the price does not change per person. The number of live chat agents varies by plan.
Questions from people who sell software
Can support be split by product?
It can. A product is a first-class entity: it has its own logo, color, knowledge base, AI agent and release notes.
Can I use only Support and keep my Jira?
You can. The modules are independent. You lose the automatic bridges (ticket becomes task, subject becomes backlog), but support works in full.
Do my customers have to learn another system?
No. They never go into bFocus: they talk to you through the widget inside your product, by email or by chat.
What if I have a system in Delphi 7?
There is a native package for Delphi 7 and for Lazarus, plus browser mode for stacks that do not support a modern WebView.
Built by a software house, for software houses
Berni Software supports its own customers in bFocus every day. Whatever does not work, we feel it before you do.