Frequently asked questions

ApprovedFlow is a cloud platform for organizations that run their work through projects. It connects planning, execution, teams, documents, approvals, and financial follow-through in one project-centered workspace.

It is designed for project-driven organizations, including professional-services firms, consultancies, engineering teams, training providers, and institutional departments. A company does not have to serve external clients to benefit from it.

No. It supports both external client engagements and internal projects. The project may have a customer outside the organization, or an internal department may act as the customer. The work still needs a scope, owner, deliverables, decisions, and a clear definition of completion.

For example, an IT department may deliver a new service to Human Resources, or a facilities team may complete work for another department. The requesting department acts as the internal customer, reviews deliverables, and confirms whether the agreed work is complete.

Not as a general-purpose ERP replacement. Its core focus is project delivery and the decisions, people, documents, and finances linked to it. The goal is to provide more structure than disconnected spreadsheets without requiring ERP-style configuration for every process.

The platform is centered on the journey from an initial request or proposal through project setup, planning, delivery, approvals, documentation, invoicing, and collection. Related records stay connected to the project rather than being scattered across separate tools.

The intended project structure supports work distributed across sites, teams, and deliverables under one overall project. Confirm the available site-level views and reporting options during your product evaluation.

Yes. The project can connect responsibilities, assignments, milestones, and documents across different teams. Each team works on its part while project leadership follows the overall delivery and pending decisions.

Yes. Project time tracking helps connect recorded effort to the work being delivered. This gives project managers a clearer view of team contribution alongside progress, responsibilities, and project costs.

Project-related travel and logistics are part of the broader project-operations direction: keeping arrangements, responsibilities, and costs linked to the project and relevant sites. Confirm which of these functions are available in the current release.

It brings tasks, deliverables, supporting evidence, and approvals into the same project context. Teams can distinguish work that has been carried out from work that has been formally accepted, so an encouraging percentage does not hide outstanding inspections or sign-offs.

Yes. External stakeholders can be invited to collaborate through controlled access to relevant project information. What each person can view or act on depends on the permissions granted to them.

ApprovedFlow is designed to keep documents, review decisions, approval history, and related project work together. Client and vendor participation can be managed through the relevant roles and approval routes, rather than relying on disconnected messages.

Documents, supporting evidence, comments, and approval decisions are linked to the related work. This makes it easier to find the relevant record, understand what changed, and identify who is expected to act next.

Yes. Its project-to-cash approach links delivery milestones and approved work to invoicing, payment evidence, receivables, and collection follow-up. The aim is to keep the financial outcome connected to what the team actually delivered.

Accounting and HR are optional modules, 5 USD per person a month each, switched on from Subscription and billing.

The product aims to keep everyday configuration simple through project-focused workflows and sensible defaults, while allowing teams to adapt how they work. Complex, organization-specific requirements should be evaluated separately rather than assumed to work without setup.

ApprovedFlow is a cloud service intended for multiple organizations. Each organization uses its own workspace and access controls; it is not a custom system built for a single named client.

Yes. ApprovedFlow supports Arabic and English as part of its multilingual approach. Language availability may differ between product areas, so confirm the experience for the screens your team will use.

They should not. Access is controlled by roles and permissions, so external clients, vendors, and internal staff can be given access relevant to their responsibilities. Review the access model with your administrator when setting up collaboration.

Every new company starts with 30 days free for 3 licences, with no card for the first 7 days. Then it is billed monthly for the licences it holds. The cost depends on the selected plan, internal users, and optional capabilities. Check the current pricing page for plan limits, external collaboration allowances, and billing terms before subscribing.

It grew out of practical experience with project delivery, disconnected systems, difficult approvals, and the gap between reported progress and what had actually been accepted. Its purpose is to make work, decisions, evidence, and payment follow-through easier to manage together.

Start with a small, representative project. Define its deliverables, invite the people responsible, set the required reviews and approvals, and assess whether the resulting progress and financial visibility meet your needs before expanding.