Founder · Product Architect · Software Engineer
In development · Testing
EzBizi brings business activity, salaried work, documents, income, expenses, tax years, projects and personal finances into one connected workspace built around the user and their accountant.
Overview
EzBizi is designed around the fact that a self-employed person can simultaneously have a business, salary, personal finances, projects and an accountant — while the underlying records still need clear boundaries.
Instead of treating business documents, salary, expenses, tax years, projects and personal financial information as unrelated lists, EzBizi connects them through attribution, time, ownership and workflow. The goal is to understand what each record belongs to and what needs to happen next.
The current application is deployed and contains working owner, accountant and admin surfaces. The product is still evolving, and regulatory or roadmap items are kept separate from implemented capabilities rather than presented as complete.
Product scope
The current application spans daily financial work, business operations, tax-year organization and accountant collaboration.
A dashboard that organizes the current financial picture, tax-year context, attention items and the sources behind the numbers.
Document intake, organization, requested documents, and issued invoices or receipts with controlled numbering and payment state.
Unified financial records with attribution, source, approval state, currency handling and business or personal context.
Businesses, employers, clients, suppliers, income sources, payslips and year-specific financial records.
Projects and operational work connected to the financial model instead of living in a separate project tracker.
Bank accounts, credit cards, loans, funds and insurance policies remain owner-only financial context.
Year-scoped income, expenses, documents and approved-only reports, plus Excel/CSV and BKMV export workflows.
A separate accountant workspace for client scope, document requests, discussion, approvals and returns for revision.
Users & workspaces
The owner, accountant and platform operator do not share one oversized interface or the same access model.
Runs the complete financial workspace: business, salary, documents, transactions, personal finance, projects and accountant handoff.
Uses a separate identity and client workspace focused on the records, requests and approvals within an authorized client link.
Operates users, platform mapping, landing content, marketing content and internal product/AI administration.
Core workflow
A shared set of concepts keeps records understandable as they move through the system.
Architecture
EzBizi is a Next.js monorepo where product behavior is primarily server-driven and financial domains share a PostgreSQL source of truth.
The architecture keeps product areas and user responsibilities separated while sharing common infrastructure where it adds value.
Engineering decisions
Selected implementation decisions show how the product keeps context and integrity explicit instead of relying on UI conventions.
Financial records explicitly carry business, employment, personal or tax context instead of inferring ownership from the screen where they were created.
This creates a durable boundary between business and private information, allows mixed records to be represented deliberately, and lets reports or accountant surfaces consume the same source records without duplicating them into separate systems.
Draft, accountant review, approval, return and locking are modeled as explicit legal transitions.
Approval behavior lives in shared domain logic rather than individual buttons, so the same rules apply consistently across screens and workflows and can be covered by automated tests.
Document numbering, money arithmetic and post-issuance behavior are designed so an issued financial record cannot quietly change underneath a report.
Issued financial documents are treated as durable records: numbering, values and later changes are handled in ways designed to preserve consistency across reporting and follow-up workflows.
Accountants do not simply log into the owner dashboard with another role.
The accountant experience is designed around the work needed for a client rather than as a copy of the owner interface, keeping responsibilities and access expectations clear for both sides.
Aliases and normalized names resolve duplicates while historical transaction text remains a document snapshot.
Canonical supplier and client rows absorb spelling variants through aliases and scoped resolution. Existing financial record text is preserved instead of being rewritten every time a canonical display name changes, protecting historical meaning.
Structured export is separated into a reusable package with mapping, encoding, validation, reconciliation and golden tests.
The BKMV export logic is isolated from the interface so it can be tested, maintained and evolved independently from the rest of the product experience.
Engineering evidence
These numbers describe the current repository structure; the automated test count is taken from the verified v2 closeout baseline.
Current codebase / verified v2 test closeout
Technology
The stack is grouped by the responsibility it serves in the system.
Claim boundary
EzBizi includes a substantial BKMV implementation and financial-document infrastructure. The portfolio presents that work as software engineering. Registration or approval by the Israeli Tax Authority is not presented as complete.
Next stage
EzBizi is in development and testing as we prepare its next stage. We’re preparing to open conversations with strategic investors who understand software for independent professionals and financial workflows.