FirmaVelo · Client discovery platform

From company research to relevant client outreach.

A full-stack workspace for freelancers to discover potential clients, research companies with source evidence, and prepare personalized outreach.

FirmaVelo concept banner showing a freelancer researching companies and preparing outreach to business leaders
AudienceFreelancers and independent professionals
ProductDiscovery, research, qualification, and reviewed drafts
ArchitectureNext.js · TypeScript · FastAPI · PostgreSQL
The problem

A relevant introduction starts long before the message.

Finding freelance clients means moving between company directories, websites, public profiles, notes, and messaging tools. The research becomes fragmented, facts are difficult to verify, and a generic pitch gives a potential client little reason to respond.

The solution

Keep the company, the evidence, and the next step together.

FirmaVelo connects company discovery, reusable research, prospect qualification, contact discovery, and editable email or LinkedIn drafts in one workspace. Freelancers can inspect why a company might fit, follow the supporting sources, and review a personal introduction before sending it through an external app.

Product walkthrough

Discover. Understand. Qualify. Introduce.

Screenshots are captures of the local application. Workspace screens use illustrative demo data, including company details, scores, contacts, credit balances, and draft text. Select a screenshot to inspect the original.

01 / Define a useful target market.

Start with services, location, industry, company size, and relevant contact roles, or import an existing company list. Advanced filters help narrow the candidates before investing in deeper research.

Advanced company search and filters in the research workspace. Demo data.
Advanced company search and filters in the research workspace. Demo data.

02 / Research the company and assess the fit.

Company profiles bring together services, projects, team-size information, and reasons a business may match the freelancer’s offering. Users can inspect uncertainty, mark a company reviewed, and add promising prospects to a shortlist.

Company pipeline, research overview, fit information, and shortlist actions. Demo data.
Company pipeline, research overview, fit information, and shortlist actions. Demo data.

03 / Inspect signals alongside their sources.

Business signals add context about projects and growth. The sources view keeps the underlying public information available for review, so a promising lead can be checked before it becomes an outreach decision.

Business signals and project context for an illustrative company. Demo data.
Business signals and project context for an illustrative company. Demo data.
Supporting source evidence remains accessible from the company workspace. Demo data.
Supporting source evidence remains accessible from the company workspace. Demo data.

04 / Find a relevant person to contact.

The contact workflow brings together decision-makers, public profile links, and available published contact information. Search leads are distinguished from stronger official-site evidence so users can judge what still needs checking.

Contact research, evidence distinctions, and outreach entry points. Demo data.
Contact research, evidence distinctions, and outreach entry points. Demo data.

05 / Prepare a draft, then review it.

Email and LinkedIn modes support editing and reviewing an introduction in the context of a selected contact. The user saves the draft, marks it reviewed, and opens the appropriate external app to send it. The displayed message is fixture content; it does not demonstrate connected LLM inference.

LinkedIn draft editor with version history and an explicit review step. Demo content; sending happens in the external app.
LinkedIn draft editor with version history and an explicit review step. Demo content; sending happens in the external app.
Engineering decisions

A workflow that spans the interface, research jobs, and account state.

  1. Next.js + TypeScriptResponsive React screens for discovery, company research, contact review, drafts, and account usage.
  2. Python + FastAPIAPI boundaries connect the workspace to research processing, public-information providers, and account operations.
  3. PostgreSQLThe production data architecture uses SQLAlchemy and Alembic migrations for persistent application state and schema evolution.

Reusable research with freshness checks

Company research is reusable rather than tied to a single viewing session. Source evidence and freshness checks support revisiting existing work, while background processing handles research tasks beyond the immediate screen interaction.

Provider boundaries

Company discovery and public-information providers include GLEIF, Wikidata, and optional Brave Search. Keeping provider integration behind the backend gives the interface a consistent research workflow across different information sources.

Workspace ownership and operations

Authentication, owner-scoped workspaces, and user/admin roles define access boundaries. Administrative monitoring provides an operational view of the application.

Credits as an accountable lifecycle

Usage credits include reservation, settlement, refunds, and a transaction ledger. This separates the balance reserved for work from its final charge and records adjustments when credits are returned.

Account balance and usage-history interface. Credit amounts shown are demo data.
Account balance and usage-history interface. Credit amounts shown are demo data.

The repository deployment setup includes GitHub Actions, Vercel, AWS ECR/App Runner, SQS, and Terraform. These describe the delivery and infrastructure configuration; they do not establish the current operating status of those services.

Responsive product design

Research and review on a smaller screen.

The responsive Next.js and TypeScript interface carries the product from its landing page into company research and message review on mobile. The supplied captures show how those tasks are presented in a narrow viewport.

Mobile landing page and product positioning.
Mobile landing page and product positioning.
Mobile company research and qualification. Demo data.
Mobile company research and qualification. Demo data.
Mobile draft editing and review. Demo content.
Mobile draft editing and review. Demo content.
More product screens
Desktop landing page and product positioning. Original application capture.
Desktop landing page and product positioning. Original application capture.
Landing-page explanation of the discovery, research, and introduction workflow.
Landing-page explanation of the discovery, research, and introduction workflow.
Product capability sections covering company context and relevant contacts.
Product capability sections covering company context and relevant contacts.
Implemented result
One workspace from a company candidate to a reviewed introduction.

The implemented workflow combines discovery, source-backed research, qualification, contacts, and editable outreach drafts with account and usage-credit management. The result presented here is the product workflow itself, illustrated with demo data. No customer-acquisition outcome or measured performance improvement is claimed.

LLM inference is not connected in the documented implementation. Messages require human review and are sent through the user’s email app or LinkedIn.

Building a product around research and decisions?

Connect a useful interface with the data, background work, and account systems that support it.

Discuss a project