About
It started with our own unreadable PDFs
Not designed in a workshop. It grew out of advisory work.
Samanegaar is now PulseUp
The name changed; the product, the team and your account did not. If you knew us as Samanegaar yesterday, we are in the same place — under a name that says more plainly what we do.
PulseUp is two halves. Pulse is what is happening right now and needs to be seen: the client who has gone quiet, the deal that has stopped moving, the engagement nobody has opened in six weeks. Up is what you do about it — because seeing, on its own, moves nothing forward.
Nothing in the product moved: no data migrated, no capability removed, no price changed. If the address you sign in at ever changes too, you will hear it from us first, and separately.
How it happened
A command-line tool
The first version: point it at a PDF, get Markdown back. It existed because a team was spending days transcribing scanned financial statements — mostly Persian, often photographed, always due tomorrow.
Reading was the easy half
The hard half was everything the reading was for: which client this belongs to, which engagement, who validated it, which figure ended up in the report, and where that figure came from. So the tool grew a spine — clients, engagements, a spreader, analysis — and became a platform.
Opinionated, from real mandates
Every part of it was built while real work was running. That is why the product is opinionated in odd places: the stage history cannot be edited because someone once edited a pipeline before a partner meeting, and validation exists as a state because a model transcribed a number wrong and nobody caught it in time.
And a wish for the name
The best fate a name can have is to become a verb — the way nobody says "search for it on a search engine". We are working toward the day someone in your office says "put it in the Pulse" and everyone knows what it means: what was said no longer gets lost.
What we believe
Six principles you can see in the product
Evidence over assertion
A figure without a source is a rumour. Spreads cite pages, adjustments carry documents, answers link to what they read.
Failures are reported, never swallowed
A page that could not be read is named with its reason. A run that produced nothing is failed, not "done". Silent loss is the worst outcome in financial software.
The model drafts, a person decides
Validation, review gates and proposals exist so that no professional ever signs something a model produced unchecked.
Your practice, your taxonomy
A new workspace starts with an empty catalogue on purpose. We will not seed another firm's idea of your service lines.
History that cannot be rewritten
Some tables have no update path and no delete path. That constraint is the product feature, not a limitation of it.
Say what is not built
We publish the gaps — in the documentation, in the sales conversation, and on this page. It costs us deals occasionally, and it is still the right trade.
The shape of it
How the platform grew
A reader
A command-line engine that turns PDFs into Markdown with a vision-language model, tuned for Persian and financial tables.
A web application
Uploads, a job queue, a document lifecycle and page-by-page human validation.
Clients and engagements
A registry, a contacts directory, engagement teams, and a pipeline with an audited stage history.
The spreader and analysis
Statements onto a chart of accounts with citations, and ratios computed from reviewed spreads.
The weekly rhythm
Feeds, voice capture, weekly summaries, and actions with owners.
Diligence and FP&A
QoE, working capital and net debt schedules with evidence; budget variance, driver notes and rolling forecasts.
The assistant, then tenancy
Hybrid cited search with approved actions — and then workspaces, roles, invitations and an AI usage ledger, which is what made it a product other firms could run.
The honest list
What we have not built
This list is maintained deliberately. If any of it is a blocker for you, say so early and we will tell you whether it is on the roadmap or not.
- Valuation models — a reserved surface, not a shipped feature
- Generated client deliverables (reports, packs) beyond export
- Billing and invoicing inside the product
- Single sign-on and directory provisioning
- Outbound webhooks and packaged connectors for specific accounting or CRM products
- SOC 2 or ISO 27001 certification
- Automated self-service tenant export — today it is an operator task on request
- Client-facing portals; feeds and workspaces are internal by design
Where it runs today
In production, in Persian, every working day
The platform runs a working advisory practice — clients, engagements, documents, weekly meetings and diligence files — which is why the roadmap is shaped by real friction rather than by a feature matrix.
It is deployed as the same four-container stack we hand to customers, and upgraded through the same tagged-release path.
- Used daily on Persian-language client work
- The same build for cloud and on-premises
- Roadmap driven by mandates, not by competitors
- Sama AdvisoryBusiness24 / 30
- Kavir PartnersTeam7 / 10
- Group TreasuryEnterpriseunlimited
About us
Who is behind PulseUp?
A small product and engineering team working alongside a financial and economic advisory practice. That proximity is deliberate: the people who file the bug are the people who lose the afternoon to it.Is the platform available outside Iran?
Yes. The interface ships in Persian and English, Arabic documents are read, and the on-premises deployment has no regional dependency. Pricing outside Iran is quoted on request.Can we talk to an existing customer?
Ask during evaluation. We will arrange a reference conversation where the customer has agreed to it — and we will not invent one where they have not.
Bring us your hardest file
Rather than talk about the product, we would rather show it working on a document you already know — and answer anything you ask, directly.