General capture
Save or copy contact information from webpages: name or label, phone, email when available, source URL, local context, confidence and relevant alternatives.
Browser-first capture
Capture contacts from the web, then turn them into reusable team data.
QuickContact starts with browser capture: save or copy the contact details you find on a page today, move them into structured rows next, and add vertical schemas when your workflow needs richer fields.
Firefox is the live extension path today. Chrome store review is in progress, Edge publication is next, and Android is part of the upcoming cross-device flow rather than the main launch message.
Browser capture -> structured row -> vertical schema
Live browser capture
Structured exports early access
Vertical schemas planned
{
"pageCapture": {
"name": "Marta Silva",
"phone": "+351 912 000 321",
"email": "marta@example.com",
"sourceUrl": "https://example.com/listings/id1icf4",
"context": "Agent block on listing page"
},
"resolution": {
"confidence": 0.91,
"alternatives": ["Leasing Desk", "Azul Imobiliaria Office"]
}
}
General capture
Saves the contact with name or label, phone, email when available, source URL, confidence and nearby context.
Structured output
Turns the page into a reusable row that is stable, spreadsheet-ready and easier to share across team history and exports.
Live focus: browser extension
The current product story starts in the browser, where teams already research, review listings, open directories and handle support pages.
Next step: structured team rows
Structured exports are the premium team workflow: cleaner fields, repeatable rows and less manual cleanup before CSV or spreadsheet handoff.
Advanced layer: API and integrations
The API already exists, but it should be framed as the advanced layer for teams, internal tools and integration-heavy workflows.
Product ladder
One capture stack, three levels of output.
General capture saves the contact. Structured capture turns the page into reusable rows. Vertical capture understands the fields your team actually needs.
Structured output
Turn the page into a reusable structured row with stable fields that are ready for spreadsheets, CSV export, team history and downstream review.
Vertical schemas
Apply planned schemas for real estate, recruiting or sales, and support ops so teams can extract the fields that matter to each workflow. These are coming next and available selectively for pilot teams.
Launch state
What ships now, what comes next, and what stays advanced.
The site now needs to tell the truth clearly: the browser extension is the live focus, structured exports are early access, vertical schemas are planned, Android is upcoming, and the API is for advanced team use.
1
Browser extension
Use the extension to save or copy contacts directly from the page with source context attached to the capture.
2
Structured exports
Request early access if your team wants page captures turned into stable rows for exports, handoff and shared history.
3
Vertical pilots
Real estate, recruiting or sales, and support ops schemas are planned for paid team add-ons and pilot workflows rather than general launch claims.
4
API and Android
The API is ready for advanced integrations, while Android belongs to the upcoming cross-device flow and open testing path.
Vertical paths
Planned schemas for the workflows that need more than a saved contact.
Each vertical page explains what teams can capture today, what structured exports add next, and which schema fields are planned for pilot teams.
Real estate
Move from listing-page contact capture toward structured property rows with property title, price, address, listing ID and agent fields.
Recruiters and sales
Capture public contact research now, then prepare structured rows for people, role, company, team, profile URL and source platform.
Support ops
Start with ticket and portal contact capture, then add queue, ticket ID, callback number, owner, issue summary and source system fields.
Value framing
Price the workflow depth, not just the capture event.
This framing keeps the product honest while avoiding a hard public commitment to final pricing before the rollout settles.
Base workflow
General capture
The live browser workflow for saving or copying contact information from webpages with useful source context.
Baseworkflow
Best for individual capture, quick save flows and early browser-first adoption.
- Name or label, phone and email when available
- Source URL, context and confidence-aware review
- Good starting point for extension-led usage
Premium/team
Next step
Structured capture
The premium team workflow for turning page captures into reusable rows that are stable enough for exports and shared review.
Premiumteam workflow
Best for teams that need spreadsheet or CSV-ready output, repeatable fields and history across multiple captures.
- Stable row output for exports and shared pipelines
- Early access for structured exports is open now
- Designed for teams, not just individual saves
Team add-on
Vertical schemas
Workflow-specific extraction for teams that need richer fields than a general contact capture can provide.
Pilotadd-on
Vertical schemas are planned as paid team add-ons because they extract richer, workflow-specific data.
- Real estate, recruiting or sales, and support ops field sets
- Positioned for early access and pilot teams, not broad launch claims
- Best fit once structured exports are already valuable to the team
Docs and rollout
Keep the advanced layers available without letting them overshadow the main story.
API docs
The API stays available for advanced team integrations, internal tooling and partner workflows.
App flow
The Android page should be read as the upcoming cross-device flow and open-testing path, not as the primary launch surface.
Privacy and terms
Keep operational, legal and reviewer-facing pages easy to reach while the browser extension rollout continues.
Structured exports
Request early access for structured exports
Join the early-access list for reusable row output. If you are evaluating a vertical schema, use the matching landing page so the request stays tied to real estate, recruiters or support ops.