Development project flow
From the first study to launch, crossing new business, legal, engineering, sales and finance.
- Stages with an owner and a deadline
- Alert before the delay, not after
- Comparable history across projects
- Dashboard for leadership
Operations consultancy · Recife, Brazil
The problem is not the system. It is the flow between them.
We work with companies that carry their own credit portfolio, run several branch offices and depend on ERPs nobody wants to touch anymore. We map the whole operation, show where money and deadlines are leaking, and build the layers that are missing, without replacing what already works.
Three layers
- 01OperationsWhere the process stalls
- 02SystemsWhere data gets lost
- 03EngineeringWhat we build instead
What we usually find
Symptoms that repeat
None of them get solved by buying another system. All of them surface during mapping, before any proposal.
- 01
A custom ERP built years ago, frozen on an old version, expensive to maintain, with support that no longer keeps up with the operation.
- 02
Receivables and payables automation started years ago, changed direction several times, and never closed a full cycle.
- 03
A sales CRM and a collections CRM that do not talk to each other, with integrations that stop exactly where the customer needs an answer.
- 04
Team centralization that cut cost on paper and collapsed local service, with an unsustainable portfolio per person.
- 05
A development project that reaches launch and only then finds a documentation blocker, after the campaign and the investment are already spent.
Engagement fronts
Three possible entry points
They can be hired in sequence or as a single program. The first delivers value in weeks, the third reorganizes the operation from within.
Technical interlocution
We take over the conversation with every software vendor the client already has, in technical language and with deadline follow-up.
- Single backlog per vendor
- Written specification before each request
- Acceptance testing before sign off
- Contracts and roadmaps under review
Central operations hub
A layer that gradually absorbs receivables, communication, customer portal and collections, keeping the ERPs in place.
- Migration module by module, no big bang
- Single source of data across systems
- Configurable collection cadence
- Real time indicators
Case in progress
One portfolio, two ERPs and no single view
A land developer that sells lots on long installment plans, directly to the buyer with no bank in between. The company itself carries the credit risk of the entire portfolio, and every contract runs through years of billing, collection and renegotiation.
Name, numbers and vendors stay with the client
What we found
- 01
Two ERPs, each with its own database, and a collections CRM duplicated to follow each of them.
- 02
The same renegotiation done in a few clicks on one base and by hand, directly in the ERP, on the other. For the customer, there are two companies.
- 03
Launches tracked in spreadsheets kept by each department. Leadership only sees a delay when the department brings it to the monthly meeting.
- 04
An earlier attempt at automated customer service that did not hold up, and little appetite for another large migration.
What we proposed
Development project flow
Each department updates the stages it owns, from land intake to post launch. Leadership follows the consolidated view without waiting for the meeting.
- Configurable stages, no development needed
- Delays flagged automatically from the deadline
- Access by department and a log of who changed what
30days, proposed delivery
A single base on top of both ERPs
A layer that reads from and writes to the ERPs and the CRM through their official APIs, consolidates customers, contracts and installments into one model, and gives collections a single screen, whatever the contract's origin.
- Two way sync, with queue and automatic retry
- Renegotiation in the same flow for both bases
- Documented API for service, website and leadership
45days, proposed delivery
Systems of record
ERP 1
ERP 2
Collections CRM
Stay as they are.
FORGE hub
Single data model
- Connectors through official APIs
- Two way synchronization
- Log of every read and write
- Integration health dashboard
Who consumes it
Collections operator
Automated customer service
Website and customer portal
Leadership dashboard
Without knowing which ERP the customer came from.
- 01
The ERPs stay
They remain the accounting and tax record. The hub works on top of them, not in their place.
- 02
Gradual cutover
One company of the group at a time. None moves before its own collections team signs off.
- 03
Security by design
Encryption at rest and in transit, two factor access, role based permissions and a log of every change. Personal data handled under LGPD.
What stays with the client
What we deliver
Every phase produces a concrete artifact, not just a meeting. What is listed here exists as a file, an environment or logged training.
- 01
Process map by area
- 02
Tool and integration tree
- 03
Bottleneck report ranked by impact
- 04
Written specification for each deliverable
- 05
Production environment with access for each area
- 06
Usage training
How we work
A program in phases, each with its own deliverable
No phase starts before the previous one is accepted. Scope is closed per phase specifically to avoid the rework that shows up when demand changes every two months.
- 00no cost
Diagnosis and mapping
Interviews, tool tree, the real flow of each process and a report ranking bottlenecks by impact. No cost and no commitment to continue.
- 01
First front in production
The chosen priority ships: closed scope, short deadline and real use by the areas involved before any expansion.
- 02
System integration
We connect ERPs, CRMs and the portal through a single source of data, eliminating double entry and manual reconciliation between bases.
- 03
Financial automation
Settlement, collection cadence, renegotiation and invoicing start running on their own, with exceptions handled by people and the rest by machine.
- 04
Operation on platform
The hub takes over day to day work for the areas, with license and continuous support, live indicators and evolution agreed on quarterly.
Who does the work
Two founders, no layer in between
Whoever interviews the operation is the same person who writes the code. There is no sales team handing the project to another team after signature.
Four years of experience building software systems. Expertise in automation, AI systems and cloud architecture, to keep solutions available 24 hours a day, functional and, above all else, secure.
- years building systems
- 04
- founders, from diagnosis to delivery
- 02
- hours a day of availability as a design target
- 24
Engineering and systems
Architecture and delivery
Integrations, automation and custom platforms. Responsible for architecture, delivery and the technical conversation with existing vendors.
Operations and process
Mapping and rollout
Process mapping, flow design and rollout with the areas involved. Responsible for making sure what was built enters the daily work of whoever operates it.
How it starts
Three steps before any proposal
The order is fixed because each step depends on the one before it. There is no proposal without a visit, and no visit without the first conversation.
- 01
Listening conversation
How the operation works today, where it hurts and what has already been tried.
- 02
On site visit to the office
We see the real process, not the described one. That visit is where mapping actually starts.
- 03
Proposal with closed scope
Only after the visit, with priority, deadline and acceptance criteria defined.
Frequently asked questions
Before you ask
Do you replace the current ERP?
No. The existing ERP stays in place. We build the integration, automation and visibility layers that are missing on top of it, instead of proposing a full migration.
How long until the first front goes live?
It depends on the scope defined in phase 00, but phase 01 is designed specifically to have a short deadline and closed scope, with real use by the areas before any expansion.
Who does the work after the contract is signed?
The same two founders who did the diagnosis. There is no handoff to another team and no sales layer between signature and delivery.
How are scope changes handled along the way?
Every phase has closed scope before it starts. A change becomes a new phase or a formal adjustment to the current one, always with deadline and deliverable reviewed in writing.
Products
WhatsApp receptionists, installed by us
Two products that answer on WhatsApp with AI. FORGE installs, configures and maintains them: you configure nothing.
For professionals and small businessesIrisAnswers on the number you already use, in seconds, at any hour. Connects by QR code in about two minutes.from R$197per monthMeet Iris For companies and teamsHermesRuns on the official WhatsApp API, books on your calendar, sends reminders and follow-ups, and puts several attendants on one number.from R$497per monthMeet Hermes
Contact
Start with the mapping
The first conversation is about listening: how the operation works today, where it hurts and what has already been tried. The proposal comes only after the visit.
Emailbrandon@forgeoperations.com.brlucas@forgeoperations.com.br
For what needs to stay on record: scope, documents and decisions.
WhatsApp+55 81 99449-2360+55 81 98830-5738
For what cannot wait: a quick question, an adjustment, the day's alignment.