Operating partners and company leaders can address recurring document problems with a common set of FormKiQ Business Solutions. Start with contracts, supplier records, or another operational need, then reuse the application and review patterns across companies while configuring each deployment for its local requirements.
The portfolio deployment model
Reuse the solution. Keep each company in control.
Start with a FormKiQ Business Solution at one company, then adapt the proven application and review process for the next.
Reusable across the portfolio
A common FormKiQ Business Solution
- Application screens
- Document models
- Review processes
For example: contract management with optional AI extraction and human review.
Deploy and configure for each company
Company A
Its own AWS account
- Its documents, dossiers, and entities
- Its users, policies, and integrations
- Its region and encryption-key controls
Company B
Its own AWS account
- Its documents, dossiers, and entities
- Its users, policies, and integrations
- Its region and encryption-key controls
What is reused, and what stays company-specific?
Reuse the application pattern
FormKiQ-delivered screens, document types, metadata fields, entity and dossier relationships, and document-review patterns provide a starting point for the next company. Optional AI extraction definitions can follow the same reviewed approach.
Configure local responsibilities
Each company confirms its owners, access roles, retention rules, AWS regions, keys, and API integrations. When using Bedrock, its model and inference profile must match the approved processing geography.
Portfolio reporting can use explicitly approved outputs through an agreed export or API integration. Reusing a solution does not grant access to another company’s documents.
Explore an example inside one company: contract renewal actions
See how one company uses the Contract Management Business Solution to connect agreements, check AI suggestions, and assign the next renewal action. The same application pattern can be adapted for another company; PORT-1042 remains this company’s contract file.
Example in FormKiQ · fictional data
One company’s contract, from review to renewal action
1. Open the company’s contract file
Procurement links the supplier agreement and latest amendment. The application shows the contract owner and documents in the portfolio company’s own AWS deployment.
How FormKiQ handles this step
- Supplier entity SUP-042: provides the company’s reusable supplier record, linked to the signed agreement and subsequent amendments.
- Contract dossier PORT-1042: connects the contract owner, business information, and source documents; each document keeps its own versions and permissions.
- Business Solution application: presents the file to the company’s authorised procurement users within its own AWS deployment.
2. Propose renewal and notice information
FormKiQ proposes renewal and notice information using Amazon Bedrock. The owner sees the suggested values with their source documents before accepting them.
How FormKiQ handles this step
- AI Processing and Analysis: uses Amazon Bedrock through the company’s AWS account with the model and inference settings approved for that deployment.
- Business Solution application: shows the suggested renewal date and notice period with source references, making the latest amendment available for comparison.
- Contract dossier PORT-1042: connects the extraction output and source documents; proposed values remain separate from the accepted business information.
Model and inference-region settings follow the company’s approved deployment configuration. The proposed values remain unapproved until reviewed.
3. Confirm the notice deadline against the amendment
The owner finds that the amendment requires 60 days’ notice instead of 30. They correct the proposed information and confirm the deadline before approving it.
How FormKiQ handles this step
- Contract information review document: records the source references, the correction from 30 to 60 days’ notice, and the deadline confirmed by the owner.
- FormKiQ workflow: routes the review document to the authorised contract owner and records the decision and comments on the submitted information.
- Business Solution application: saves the accepted renewal date and notice deadline; PORT-1042 retains the original proposal, corrected information, and approval evidence.
4. Assign and record the renewal action
Procurement assigns an owner and target date before the notice deadline. The owner records the decision and adds the resulting supplier correspondence to the contract file.
How FormKiQ handles this step
- Business Solution application: shows upcoming renewal work using reviewed dates, with a named action owner, target date, progress, and next action.
- Decision and correspondence documents: retain the authorised renewal decision and reasons, together with supplier notices, replies, or revised terms added by staff.
- Contract dossier PORT-1042: connects the action history and correspondence to the accepted dates, approval evidence, agreement, and amendments within the company’s deployment.
Authorised staff decide whether to renew, renegotiate, or end the agreement. Sending notices uses the company’s agreed communication process.
Renewal action, decision, and correspondence connected to PORT-1042
Start with a business process your companies share
These are packaged applications for daily work, supported by FormKiQ documents, dossiers, entities, workflows, and APIs. The portfolio approach reuses that foundation while accommodating different company systems and responsibilities.
Contract Management
Connect agreements and amendments, review terms, and assign renewal or termination actions before notice deadlines.
Explore the contract workflow →
Supplier Documents
Define required evidence, review replacement certificates, and keep renewal responsibilities visible to procurement.
Explore the supplier workflow →
Employee Records
Follow onboarding, policy acknowledgements, employment changes, and offboarding in a governed employee file.
Explore the employee workflow →
Other starting points include financial applications and agreements, records management, and policies and procedures.
Build on the first deployment
1. Prove one use case
Choose an operational owner, configure the Business Solution, and validate it with real document types and agreed acceptance criteria at the first company.
2. Capture what can be reused
Agree the application behaviour, record model, review process, and optional AI extraction definitions that should become the next company’s starting point.
3. Adapt and operate locally
Configure the next company’s roles, retention requirements, regions, and integrations. Confirm the process with local owners and measure outcomes against its agreed baseline.
Add AI where it helps the operational work
Use Amazon Bedrock through the company’s AWS account to propose contract terms, classify documents, or prepare summaries. The Business Solution presents the source records and routes proposed information for human review before using accepted values in the process.
Keep processing choices local
The selected model and inference profile must match the company’s approved processing geography. Each deployment defines its access, logging, and retention requirements.
Keep decisions traceable
Connect the source document, AI proposal, correction, and review decision to the business file. In the contract example, the owner checks an amendment before acting on a notice deadline.
Keep company ownership clear as the portfolio changes
Company-owned deployments keep infrastructure, records, and operational responsibilities identifiable through acquisition, growth, and exit. Access changes, integrations, licences, and any transition work are planned for the transaction.
When the operating team needs portfolio reporting, agree which reviewed outputs may be shared, who may receive them, and how an export or API integration will deliver them. Company access permissions continue to govern the underlying records.
This approach fits portfolios seeking repeatable document operations with local ownership, including regulated businesses with residency requirements. For fund accounting, investment valuations, or performance reporting, use the relevant portfolio or finance system; FormKiQ supplies the document and workflow layer.
Choose the first company and the first process
Bring one recurring document problem, its business owner, and the requirements that differ across companies. We will identify a suitable Business Solution, its configuration and integration scope, and what can carry into later deployments.
- Current process, document types, and measures of success
- Company AWS ownership, residency, security, and operating responsibilities
- Application configuration, edition/module needs, and API integrations
- Optional AI processing, review requirements, and approved reporting outputs
