Business process automation for the forms, approvals and documents that still move by email
Business process automation replaces a manual office process, such as a form passed by email for signatures, with a system that routes the request, enforces the rules, produces the document and updates the ERP. Goldenroz builds these automations for organizations of roughly 100 to 2,000 employees that run an ERP and Microsoft 365, using Power Automate where it is enough and custom code where it is not. The company owns the result. Projects start at $25,000 at a fixed price per phase after a free one-hour scoping call.
From $25,000, fixed price per phase
Updated 2026-11-15. By Shai Goldenberg
What usually goes wrong
- A form that travels by emailA purchase request is a spreadsheet attached to an email. It collects four approvals by reply, and the requester has no way to see where it is stuck.
- The same data typed three timesA clerk copies details from a form into the ERP, then into a Word template, then into a tracking spreadsheet. Each copy is a chance for an error.
- Rules that live in one person's headWho approves above which amount, and what happens when the approver is on leave, is known to one veteran employee and written nowhere.
- Flows nobody maintainsDozens of automations were built by different employees under personal accounts. Some fail silently, and no one has a list of them.
- A subscription for every small needEach department bought its own tool for forms, signatures or task tracking. The yearly total is large and the tools do not share data.
What is included
- Process mapThe current process written down step by step with the people who do it: who starts it, who approves, what data is used and where it ends. Exceptions are listed, because they decide the design.
- FormsDigital forms with validation, fields filled in advance from the directory and the ERP, attachments and a draft state, usable on a phone.
- ApprovalsRouting by amount, department and role, with substitutes, reminders, escalation after a set time and approval from an email or a Teams message.
- Document generationContracts, orders, certificates and letters produced from a template with the approved data, saved to the right library with a version and a reference number.
- ERP and Microsoft 365 integrationReading and writing to the ERP through its API, database or file interface, and to SharePoint, Outlook and Teams through Microsoft Graph. Each integration is priced as its own line.
- Log, monitoring and handoverA record of every request and decision, alerts when a step fails, and documentation so that your IT team can run and change the automation.
Workflow automation software: when Power Automate is enough
For an organization on Microsoft 365, Power Automate is workflow automation software that is often already paid for. It is enough when the process is linear, the data lives in SharePoint lists, Outlook and Teams, volumes are modest and the logic fits in a flow a second person can read. Our Power Automate consulting page covers that work.
Custom code is the better choice when the process has many branches and exceptions, when it must write to the ERP inside a transaction, when the volume is high, when data must stay on your own servers, or when the connectors you need carry extra licence costs for every user. In those cases a small application with a real database is cheaper to maintain than a large set of flows.
Many projects use both: a custom service for the core logic and the ERP, and a flow for notifications and approvals in Teams. We decide per process and write the reason down.
Internal tools the company owns
Internal tools are the small applications that sit between the ERP and the people: a request screen, an approval queue, a report, a tablet form on the factory floor. Owning them means the repository is in your organization, the database is on your servers or in your cloud account, and no vendor charges per user.
At an industrial company with about 400 users, where Shai ran IT for four years, he presented management with an estimate that replacing rented internal systems with systems the company owns could save about 800,000 NIS a year, roughly $250,000. It is an estimate presented to management, not a measured result. The systems behind that kind of estimate are listed on the internal systems page.
HR automation and other processes to start with
HR automation is a common first project because the processes are frequent and well defined: leave and overtime requests, salary change approvals, employment letters, training sign-off and the joiner and leaver process, which has its own page under employee onboarding automation.
Outside HR, the usual candidates are purchase requests, supplier and customer credit approvals, engineering change requests, quality deviations and expense claims. A good first process runs often, involves several departments and has a clear end. We pick it with you on the scoping call and price it as one phase.
How the work runs
Scoping call
Before the projectA free one-hour call with Shai. We go through the process, the systems you already run and whether a product you can buy would do the job. You leave with a list of phases and a fixed price for the first.
Process and data model
Week 1Entities, statuses, roles and integration points are decided and documented with the people who do the work. This is the part that is expensive to change later.
Foundation
Weeks 2 to 3Login, roles, permissions, the core tables and the deploy pipeline go live on staging before feature work starts.
Feature phases
Phase by phaseEach phase has a fixed scope and price and ends with working software on staging. A small group of real users tries it, and you approve it before the next phase is priced.
Rollout and handover
Final phaseData import from the old tools, user training, production cutover, monitoring and documentation. Maintenance and support after launch are quoted separately.
What it costs
Every project is split into phases. Each phase has a fixed scope and a fixed price, agreed before work on it starts. Hosting, licences and third-party services are paid directly by you.
- Business system, first phase and smaller systemsFixed price per phaseFrom $25,000
- Larger systemsWeb, mobile and several integrations, scoped one phase at a time$100,000 and up
- Maintenance and supportAgreed after launch, not requiredQuoted separately
- Scoping callOne hour with Shai$0
- Code ownershipRepository in your organization from day oneYours
Who it is not for
- A single simple flow, such as a notification when a file is added. Your own Microsoft 365 administrator can build it in an hour.
- Processes whose rules the company has not agreed. Software cannot settle a dispute between departments.
- Robotic screen automation of legacy applications as a long-term answer. We integrate through APIs, databases and files where they exist.
Who does the work
Shai leads the technology side: business software, SaaS and mobile apps, payments and escrow systems, Postgres security, AI agents built with Claude Code and MCP, and IT and infrastructure projects with senior infrastructure engineers.
Questions buyers ask
What is business process automation?
Business process automation is the use of software to run a repeatable office process from request to completion: collecting data in a form, routing approvals, creating documents and updating business systems. People still make the decisions. The software moves the work, applies the rules and keeps the record.
What is the difference between workflow automation software and custom development?
Workflow automation software, such as Power Automate, lets you assemble a process from ready connectors with little or no code. Custom development writes the process as an application with its own database. The first is faster for simple processes, and the second is easier to maintain when logic, volume or integrations grow.
How much does business process automation cost?
At Goldenroz, projects start at $25,000 at a fixed price per phase, quoted after a free one-hour scoping call. A phase usually covers one process or a small group of related ones. The main cost drivers are the number of exceptions and the ERP integration.
Which processes should we automate first?
Start with a process that runs many times a month, crosses several departments and causes visible delays, such as purchase requests or leave approvals. Avoid starting with a rare process or one whose rules are still disputed. Agreeing the rules is half the project.
Can the automation run on our own servers?
Yes. Custom automations can be installed on a server inside your network, next to the ERP database, with sign-in through Microsoft Entra ID or Active Directory. Power Automate flows run in Microsoft's cloud and reach on-premises data through the on-premises data gateway.
What are the best business process automation tools?
It depends on where your data lives. For organizations on Microsoft 365, Power Automate covers many approval and notification flows. Workflow products with visual builders suit standard processes. Custom code is the better choice when a flow needs complex rules, heavy integration with an ERP, or must run on your own servers. We choose per process and say why.
Guides on this topic
- A 5-year cost model for build vs buy software, one company's real subscription figures, and the cases where buying off the shelf is still the right call.
- Twelve business process automation examples from HR, finance, IT and operations, with the right tool for each and a scoring method to pick your first project.
- OneDrive holds one person's work files. SharePoint holds what a team or the company owns. See where Teams files live and how to set external sharing.
Talk to the person who will do the work
One hour, no sales team. You talk to Shai Goldenberg, the CTO, about your systems or your product, and you leave with a clear next step and a price range.