20 Practical and Ready-to-Run DeepResearch Workflows for Businesses

Day 20 of 30 Days of Search.

A product lead needs to compare pricing before changing a plan. A deal team needs acquisition candidates, not another industry overview. A biotech team needs to separate an approval pathway from a reimbursement problem.

Those are different research jobs. They need different questions, sources and outputs.

A Valyu DeepResearch workflow is a versioned research template that defines inputs, research instructions and requested outputs. This guide covers twenty Valyu-curated, prebuilt templates you can run with a market, company, technology or other assignment. Each run creates a research task; cited reports and requested files still need verification.

TL;DR

• Twenty workflows, no repeats. These are different from the ten in 10 Ready-to-Run DeepResearch Workflows for Finance, Life Sciences, and Supply Chain. Read that guide for company profiles, trading comparables, earnings previews, commercial diligence, trial and pipeline research, and supply-chain workflows.
• Choose the job before the mode. Market sizing, pricing research, acquisition screening, regulatory analysis and sales preparation each have a different output contract.
• Preview first, verify after running. Previewing does not launch paid research. Runs consume credits, source access varies, and requested files need their own completion checks.

How these twenty workflows were selected

Valyu has a curated catalogue of 44 workflows. The twenty below span seven catalogue verticals: consulting, private equity, investment banking, hedge funds, life sciences, legal/regulatory and sales intelligence. The catalogue and template fields can be inspected through the Workflows API.

Market Sizing, Market Map and Investment Committee Memo are three very popular deepresearch workflows I've seen teams use often!

For the other seventeen, the selection criteria were a distinct decision to support, a concrete deliverable, a useful example that can be supplied through the declared inputs, and limited duplication within the list. This is a curated guide, not a benchmark or proof that one template outperforms another.

The example situations are illustrative unless explicitly identified as a live run. Requested outputs describe the template's instructions, not guaranteed findings or file-generation success.

The 20 DeepResearch workflows at a glance

#	Prebuilt workflow	The job it helps with	Requested files
1	Market Sizing (TAM/SAM/SOM)	Test whether a defined market merits investment	Excel, PowerPoint
2	Pricing Strategy Benchmark	Compare pricing models and packaging	Excel
3	Customer Segmentation	Prioritise customer groups	Excel, PowerPoint
4	Go-To-Market Strategy	Plan a product's route to market	Word, PowerPoint, Excel
5	Market Map	Find and organise companies in a category	Excel, PowerPoint
6	Investment Committee Memo	Prepare a first-pass investment discussion	Word, Excel
7	Add-on Acquisition Screen	Find potential bolt-on acquisitions	Excel
8	Buyer & Investor List	Research a sell-side buyer universe	Excel
9	Precedent Transactions	Investigate comparable acquisition deals	Excel
10	Long Thesis Write-up	Challenge a positive investment thesis	Word, Excel
11	Earnings Recap	Understand a completed earnings release	Excel
12	Macro Thesis Brief	Pressure-test a macroeconomic hypothesis	Excel, Word
13	Target Class Deep Dive	Review a biological target or mechanism	Excel, Word
14	Regulatory Pathway Analysis	Research drug-development regulatory routes	Word, Excel
15	Reimbursement & Payer Landscape	Investigate coverage and access hurdles	Excel, Word
16	Patent Landscape	Map relevant patent families and claims	Excel, Word
17	Regulatory Landscape	Compare rules across jurisdictions	Excel, Word
18	Compliance Gap Assessment	Prepare an obligations and evidence-gap review	Excel, Word
19	Account Intelligence Briefing	Prepare an informed enterprise sales call	Word
20	Competitive Battlecard	Prepare for a named competitive sales situation	Word, Excel

Market research and product decisions

1. Market Sizing (TAM/SAM/SOM)

A founder has a plausible product idea but an unhelpfully broad market estimate. “Customer support software” is not a useful definition if the actual buyer is a US B2B SaaS company with 50 to 500 employees.

Use Market Sizing to investigate that narrower opportunity. The template asks for top-down and bottom-up estimates, the serviceable market, an obtainable share, segmentation and sensitivity to the main assumptions. TAM means total addressable market; SAM and SOM narrow that to what the product can serve and realistically obtain. The checked version-1 prompt specifies a 2026-2030 horizon.

Example input: market: “AI customer support automation for US B2B SaaS companies with 50-500 employees.”

Workflow ID: con-market-sizing · Mode: standard · Requested files: Excel assumptions and sizing workbook, plus a PowerPoint readout. Catalogue flag: Popular.

Use the assumptions table to decide which customer-count or spending estimate needs validation next. The useful outcome is a model you can challenge, not a headline market number you must accept. A sourced industry total does not establish obtainable revenue for your product.

The actual template inspection panel. It specifies what the research should attempt; it is not a completed market-sizing result.

2. Pricing Strategy Benchmark

A product lead wants to change pricing, but competitors charge on different units. One emphasises storage, another compute, and another a combination of usage and minimum commitments. Comparing the cheapest headline price would hide those differences.

Pricing Strategy Benchmark researches value metrics, tiers, published prices, commitments, free offerings, add-ons and recent packaging changes. Its workbook separates the comparison matrix, tiers, discount signals and implications.

Example input: category: “Vector database services for a small production RAG application: Pinecone, Weaviate Cloud and Qdrant Cloud. Distinguish storage, compute, requests and enterprise quote-only plans.” RAG means retrieval-augmented generation.

Workflow ID: con-pricing-benchmark · Mode: standard · Requested file: Excel pricing benchmark.

Use the result to define a comparable workload and shortlist plans for a cost calculation. That is a better next step than declaring a universal cheapest provider. Public list prices, reported procurement experiences and negotiated net prices are different kinds of evidence.

The pricing template requests a comparison of charging units, packaging, commitments and published evidence, not just a list of headline prices.

3. Customer Segmentation

A payroll company can sell to businesses with 50 employees or 1,000, but their buying processes and requirements may differ substantially. The team needs to choose a segment before writing campaigns for everyone.

Customer Segmentation proposes groups based on needs, firmographics and buying behaviour. It asks for segment sizes, jobs to be done, buying triggers, willingness-to-pay indicators and a prioritised shortlist.

Example input: product: “A payroll and HR platform for US companies with 50-1,000 employees.”

Workflow ID: con-customer-segmentation · Mode: standard · Requested files: Excel segment profiles and priority scoring, plus PowerPoint.

Take the proposed priority segments into interviews and compare them with actual acquisition and retention data. The desired outcome is a testable customer-focus decision. Public research can suggest buying patterns; it cannot substitute for your CRM, conversion data or direct customer evidence.

4. Go-To-Market Strategy

A team launching compliance software has a feature list but no clear answer to who buys, what triggers a purchase or which channel reaches that buyer.

Go-To-Market Strategy connects the ideal customer profile, buyer roles, messaging, channels, pricing, partners, launch milestones and success metrics. The template requests a strategy document, presentation and workbook rather than treating a marketing slogan as a launch plan.

Example input: product: “An AI compliance-monitoring platform for US mid-market banks, preparing its first twelve months of commercial activity.”

Workflow ID: con-gtm-strategy · Mode: standard · Requested files: Word strategy, PowerPoint readout and Excel planning workbook.

Use the output to choose the first channel and the assumptions that need an experiment. Then assign owners and budgets outside the research tool. A researched launch plan is an informed starting position, not evidence that its proposed sales cycle or acquisition cost will hold.

Company discovery and deal preparation

5. Market Map

A deal team knows a category is interesting but keeps encountering the same familiar companies. It needs an organised company universe before deciding whom to investigate.

Market Map researches leaders, challengers, point solutions and emerging companies, with positioning, funding and traction signals. Its requested workbook includes company, tier, white-space and thesis tabs.

Example input: category: “AI customer support agents for B2B SaaS companies.”

Workflow ID: pe-market-map · Mode: heavy · Requested files: Excel market map and PowerPoint readout. Catalogue flag: Popular.

Use the map to choose a shortlist for deeper work and identify gaps in the category definition. The result should explain why a company belongs in a segment, not simply collect logos. A public-source map is not an exhaustive company census, and inferred traction is not verified revenue.

6. Investment Committee Memo

An investment team needs to decide whether a company deserves a formal diligence workstream. A company description alone does not organise the thesis, risks, value-creation possibilities and exit considerations for that discussion.

Investment Committee Memo requests that first-pass structure, with a supporting workbook covering financials, competitors, exit comparables and risks.

Example inputs: company: “Notion”; thesis: “Test whether expansion from collaborative documents into enterprise knowledge workflows supports a durable business. Separate public evidence from unavailable private financials.”

Workflow ID: pe-investment-memo · Mode: heavy · Requested files: Word memo and Excel supporting workbook. Catalogue flag: Popular.

Use the memo to approve, reject or narrow the next diligence assignment. The practical outcome is a better-framed committee discussion, not an investment decision delegated to a report. Private-company financial gaps must remain gaps until the team obtains reliable disclosures.

7. Add-on Acquisition Screen

A platform company wants to expand through acquisitions but needs to distinguish plausible targets from businesses that merely operate in the same industry.

Add-on Acquisition Screen researches segment fit, geography, product adjacency and deal-size feasibility. It requests a ranked target workbook with a shortlist, fragmented segments and integration themes.

Example input: platform: “An illustrative PE-owned US HVAC services platform in the Midwest seeking adjacent service businesses.”

Workflow ID: pe-addon-screen · Mode: standard · Requested file: Excel acquisition-target screen.

Use the shortlist to prioritise commercial checks and potential introductions. The intended outcome is a manageable sourcing queue with explicit fit hypotheses. A company appearing on the list does not mean it is for sale, that its owners want contact, or that publicly inferred size and ownership are accurate.

8. Buyer & Investor List

A sell-side adviser needs a buyer universe with a reason for each candidate's inclusion. A large organisation in the right sector is not automatically a credible acquirer.

Buyer & Investor List researches strategic and financial buyers, acquisition patterns, strategic fit, capacity signals and possible deal theses. Its requested workbook separates buyer categories and priority tiers.

Example input: target: “An illustrative profitable US vertical SaaS company serving independent dental practices, with $30 million annual recurring revenue, seeking a strategic or financial buyer.”

Workflow ID: ib-buyer-list · Mode: standard · Requested file: Excel buyer list.

Use the research to decide which candidates deserve a capacity check and a tailored approach. Treat the example revenue as supplied context, not a discovered fact. The report cannot establish confidential mandates, investment-committee appetite or willingness to transact.

9. Precedent Transactions

An analyst preparing a valuation discussion needs transaction evidence, not just a list of acquisition headlines. Deal structure, timing, buyer type and available target metrics determine whether a precedent is useful.

Precedent Transactions investigates comparable M&A deals and requests a workbook containing deal rows, summary statistics and sources. The template asks researchers to distinguish announced and final values and estimated versus disclosed metrics.

Example input: sector: “Vertical SaaS for healthcare.” The input is a sector, not a company name.

Workflow ID: ib-precedent-transactions · Mode: standard · Requested file: Excel precedent-transactions workbook.

Use the candidate table to select the most defensible precedents for manual checking. A useful outcome may be a smaller set with reliable disclosures rather than a large table of inferred multiples. An undisclosed transaction value or unavailable EBITDA figure should not become a precise number just to fill a cell.

Public-markets research

10. Long Thesis Write-up

An analyst has a positive view of a company but needs to separate a genuinely differentiated argument from enthusiasm about a good business.

Long Thesis Write-up requests business-quality analysis, unit economics, management assessment, catalysts, valuation and a bear case. It also requests supporting financial, forecast, valuation and catalyst tables.

Example inputs: ticker: “COST”; variant: “Test whether membership-fee economics and international expansion support the thesis. Actively seek contradictory evidence.”

Workflow ID: hf-long-thesis · Mode: heavy · Requested files: Word thesis and Excel supporting data.

Use the bear case and valuation assumptions to decide which claim needs further work before an investment discussion. A good business and an attractive security at today's price are separate propositions. Forecasts, inferred consensus and position-sizing suggestions require independent review; the workflow is research, not personalised investment advice.

11. Earnings Recap

After an earnings release, an analyst needs to understand what changed in the reported business and guidance. That is a different task from the Earnings Preview covered in the earlier article.

Earnings Recap researches results, guidance, segments, operating metrics and changes to expectations. Its workbook requests separate tabs for reported-versus-consensus results, guidance, segment detail, KPIs and estimate changes.

Example inputs: ticker: “MSFT”; period: “Fiscal Q4 2026, quarter ended 30 June 2026.” Specify the fiscal period rather than assuming the calendar quarter matches.

Microsoft's FY2026 fourth-quarter release confirms that quarter-end date.

Workflow ID: hf-earnings-recap · Mode: standard · Requested file: Excel earnings-recap workbook.

Use the recap to update the questions in your existing thesis. Check release dates, accounting definitions and the timestamp of any consensus estimate. Unavailable pre-release consensus cannot be reconstructed reliably from a later article that already knows the result.

12. Macro Thesis Brief

A research team has a broad view about electricity demand and data-centre investment. Before expressing that view in a portfolio, it needs to know which evidence supports the mechanism and which observations would weaken it.

Macro Thesis Brief connects a specific hypothesis with economic data, policy, positioning, cross-asset implications and risks. Its requested workbook includes data series, positioning, possible expressions and invalidation conditions.

Example input: thesis: “Test whether data-centre electricity demand is creating persistent US power-infrastructure bottlenecks. Distinguish actual demand and capacity from announced projects.”

Workflow ID: hf-macro-brief · Mode: heavy · Requested files: Excel macro workbook and Word brief.

Use the result to choose indicators to monitor and identify where the thesis may already be reflected in prices. Preserve data vintages, units and publication dates. A convincing economic narrative does not establish a profitable trade.

Life sciences and intellectual property

13. Target Class Deep Dive

A biotech team wants to investigate a mechanism before committing to a programme. The question is not only which companies have assets, but whether the biology and clinical translation justify the next experiment.

Target Class Deep Dive researches pathway biology, genetics, druggability, prior clinical outcomes, active assets, safety themes, biomarkers and key unknowns. Its requested tables separate clinical assets from preclinical work.

Example input: target: “STING agonists for solid tumours; separate preclinical evidence from observed clinical outcomes.”

Workflow ID: ls-mechanism-deep-dive · Mode: heavy · Requested files: Excel target-class workbook and Word deep dive.

Use the unresolved questions to shape a literature discussion or experimental follow-up. This differs from an indication-level drug landscape: the centre of the investigation is the mechanism and its translation. Animal results, mechanistic plausibility and demonstrated benefit in people must remain distinct. The report is not treatment guidance.

The actual target-class template separates biology, human translation, active clinical assets, preclinical leaders and safety themes.

14. Regulatory Pathway Analysis

A drug-development team needs to understand which regulatory precedents and guidance matter before assuming a trial design will support a filing.

Regulatory Pathway Analysis researches FDA and EMA routes, precedent approvals, relevant guidance, trial-design requirements, timing considerations and risk flags.

Example input: asset: “An illustrative oral PCSK9 inhibitor for primary hypercholesterolaemia in the US and EU.” The example describes a research scenario, not a claim about an approved product.

Workflow ID: ls-regulatory-pathway · Mode: standard · Requested files: Word pathway memo and Excel precedent/guidance workbook.

Use the evidence to prepare questions for regulatory specialists and identify missing development requirements. The desired outcome is a better-scoped regulatory workstream. Precedent approval timelines are not a promise for a new asset, and similarities between products do not establish identical requirements or approval prospects.

15. Reimbursement & Payer Landscape

A therapy can face a viable development pathway and still encounter difficult coverage or access conditions. A commercial team needs to investigate those conditions before treating regulatory approval as the end of the work.

Reimbursement & Payer Landscape researches payer structures, formulary or coverage dynamics, pricing references, comparable launches and evidence requirements. The requested workbook separates markets, price benchmarks, analogues and access risks.

Example input: product: “Gene therapy for haemophilia B in the US and Germany; distinguish published list prices, coverage conditions and undisclosed net prices.”

Workflow ID: ls-payer-landscape · Mode: standard · Requested files: Excel payer-landscape workbook and Word strategy memo.

Use the access-risk table to prioritise health-economics and outcomes-research questions. A useful result identifies which evidence is missing. Published policy is not a guarantee of an individual coverage decision, and a list price is not the amount a payer actually pays.

16. Patent Landscape

An R&D team investigating a material needs to understand relevant patent families, assignees and claims before deciding where specialist IP review should begin.

Patent Landscape researches filing patterns, major assignees, patent families, recent filings, expiry considerations and litigation signals. It requests both a workbook and a narrative memo.

Example input: technology: “Solid-state lithium battery electrolytes; separate patent families, jurisdictions, application status and granted claims.”

Workflow ID: legal-patent-landscape · Mode: heavy · Requested files: Excel patent-landscape workbook and Word memo.

Use the families and claim references to shortlist documents for a patent professional. Multiple national publications can belong to one family, so a raw document count can distort the landscape. The template includes freedom-to-operate callouts, but a research report does not establish freedom to operate. Current claim scope, legal status and jurisdiction need expert checking.

Regulation and compliance

17. Regulatory Landscape

A company planning a cross-border launch needs to understand which rules apply where. A single “AI regulation” summary can mix proposed legislation, guidance and enforceable obligations.

Regulatory Landscape researches jurisdictions, scope, obligations, penalties, enforcement and practical compliance implications. Its requested matrix helps compare those dimensions rather than blending them into a single answer.

Example input: topic: “AI model transparency and disclosure requirements in the EU, UK and US; distinguish enacted obligations, guidance and proposals as of 20 October 2026.”

Workflow ID: legal-regulatory-landscape · Mode: standard · Requested files: Excel regulatory matrix and Word landscape memo.

Use the matrix to identify jurisdictions and implementation dates for counsel to review before launch. Cite primary regulatory material wherever possible. A rule's announcement date, effective date and phased applicability are not interchangeable, and an overview is not legal advice.

18. Compliance Gap Assessment

A compliance lead needs to move from “this regime may apply” to a reviewable list of obligations, evidence requests and possible remediation work.

Compliance Gap Assessment researches a regime against a described company and requests an obligations table, current-state assessment, gaps and prioritised roadmap.

Example input: regime_and_company: “EU AI Act obligations for an illustrative mid-market HR software vendor supplying recruitment-screening tools in the EU. Public-information assessment only; mark unknown internal controls unverified.”

Workflow ID: legal-compliance-gap · Mode: heavy · Requested files: Excel obligations/gap workbook and Word memo.

Use the report to assign internal evidence requests, then revise the assessment with the company's actual controls and legal advice. The outcome is a starting point for a compliance workstream, not a compliance certificate. Absence of a public description of a control is not proof that the control is missing.

Sales preparation

19. Account Intelligence Briefing

An account executive has a meeting booked but needs a reason to discuss their product beyond a generic company introduction.

Account Intelligence Briefing researches the account's business, strategic priorities, public buying and technology signals, plausible pain points and relevant stakeholders. It requests tailored talking points, discovery questions and an opener.

Example inputs: account: “Schneider Electric”; our_product: “An API that supplies cited public financial, technical and regulatory research to internal research applications.”

Workflow ID: sales-account-briefing · Mode: fast · Requested file: Word pre-call briefing.

Use the briefing to choose evidence-based discovery questions, not to claim you know an account's budget or purchasing intent. Public job postings and announcements are signals, not confirmation of an active buying process. Stakeholder roles and reporting lines also need checking before outreach. This is a research example, not a claim of a customer relationship.

20. Competitive Battlecard

A salesperson knows a named competitor will be in the conversation. They need a balanced, current account of differences and useful discovery questions, not a page of unsupported claims about who is better.

Competitive Battlecard researches the two products' positioning, features, pricing, sales motion, strengths, weaknesses, objections and supporting evidence. The requested workbook separates features, objection handling, questions and proof points.

Example input: we_vs_them: “Qdrant Cloud vs Pinecone for a small engineering team deploying a production RAG application; use current public documentation and flag unsupported competitive claims.”

Workflow ID: sales-battlecard · Mode: standard · Requested files: Word battlecard and Excel supporting matrix.

Use the result to prepare a fair comparison and decide which customer requirements deserve a demonstration. Verify every competitive assertion before it reaches external material. A competitor's silence in public documentation does not prove that a feature is unavailable.

How to run a prebuilt DeepResearch workflow

From the Valyu platform

1. Open Workflows in the Valyu platform.
2. Find a template by its exact name. Inspect its inputs, instructions, requested deliverables and mode.
3. Choose Run or Run in playground, then supply the requested input values.
4. Review the populated assignment, mode and deliverables. For Excel, Word or PowerPoint output, confirm code execution is enabled before starting paid research.
5. When the run finishes, read the cited report and check each requested file separately.

The catalogue can include your organisation's private templates as well as Valyu's prebuilt ones. The selection in this article includes Valyu-curated workflows only.

Fill in the contextual fields shown in the examples, even when labelled optional. In the checked version-1 previews, omitting thesis from Investment Committee Memo, variant from Long Thesis Write-up, or our_product from Account Intelligence Briefing removed the opening input sentence containing the company, ticker or account name. All three requests returned HTTP 200. Supplying those fields retained that sentence. Inspect the resolved assignment, not just the success status.

From an application

The same workflows are available through the API. Set VALYU_API_KEY in your server first; the commands below read that variable rather than loading a .env file automatically. This REST example previews the pricing assignment without starting a research task:

curl --fail-with-body \
  -X POST "https://api.valyu.ai/v1/workflows/con-pricing-benchmark/preview" \
  -H "x-api-key: $VALYU_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "workflow_version": 1,
    "workflow_params": {
      "category": "Vector database services: Pinecone, Weaviate Cloud and Qdrant Cloud. Compare current public pricing and distinguish storage, compute, requests and commitments."
    }
  }'

Starting the actual research is a separate, credit-consuming request:

curl --fail-with-body \
  -X POST "https://api.valyu.ai/v1/deepresearch/tasks" \
  -H "x-api-key: $VALYU_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "workflow_id": "con-pricing-benchmark",
    "workflow_version": 1,
    "workflow_params": {
      "category": "Vector database services: Pinecone, Weaviate Cloud and Qdrant Cloud. Compare current public pricing and distinguish storage, compute, requests and commitments."
    },
    "mode": "standard",
    "tools": {
      "code_execution": { "enabled": true }
    }
  }'

Save the returned deepresearch_id as the shell variable TASK_ID. Check its status rather than creating another task if a client disconnects:

curl --fail-with-body \
  "https://api.valyu.ai/v1/deepresearch/tasks/$TASK_ID/status" \
  -H "x-api-key: $VALYU_API_KEY"

Read the workflow quickstart for SDK examples and the workflow reference for supported overrides. A workflow request supplies workflow_id and workflow_params; do not combine it with the mutually exclusive freeform query, input, research_strategy or report_format fields.

Five checks before using the output

Check source access. A template can ask for a source without guaranteeing your account can access it. Proprietary databases named in research instructions are source priorities, not a promise of licensed database access. Review the current data-source coverage.

Check dates and definitions. Financial periods, study endpoints, regulatory dates and price units can change the meaning of a comparison. Preserve those details in tables and downstream applications.

Check claims against citations. A citation is a route to inspection, not proof that the linked source supports the claim. Open the important sources, and keep estimates, inference and reported facts separate.

Check tools and files. Excel, Word and PowerPoint generation requires code execution. The twenty previews inspected here returned empty tool settings, so the live examples explicitly enabled it. A completed research task and a completed deliverable are separate checks; verify file status and open the file.

Check costs and repeatability. Previewing is free; runs and optional capabilities consume credits. These previews returned estimated_credits: null, so do not treat a missing estimate as zero cost. Consult current pricing. Pinning version 1 preserves template configuration, not live facts, source availability or identical results.

Frequently asked questions

What is a DeepResearch workflow?

A Valyu DeepResearch workflow is a versioned template for a repeatable research job. It defines inputs, research instructions, source strategy, report structure, requested deliverables and recommended settings. Each execution creates a DeepResearch task.

Which DeepResearch workflow should I try first?

Choose the output you need next. Start with Pricing Strategy Benchmark for a pricing comparison, Market Sizing for an opportunity model, or Account Intelligence Briefing for meeting preparation. A narrower assignment is easier to verify than a broad request to research an entire industry.

Are these the highest-rated Valyu workflows?

No user-rating scores or usage counts were returned by the inspected catalogue. This guide includes the three eligible templates marked Popular and seventeen further editorial selections. It is not a measured quality ranking.

Are these different from the earlier ten-workflow article?

Yes. None of the twenty workflow IDs here appears in 10 Ready-to-Run DeepResearch Workflows for Finance, Life Sciences, and Supply Chain. Together, the articles cover thirty distinct prebuilt workflows. An earnings recap looks backwards at a release; the earlier earnings preview prepares for one.

Do I need to build an agent or supply a separate model API key?

Not for these prebuilt runs. The platform provides a manual route; API execution uses a Valyu key and the saved workflow's inputs. Valyu DeepResearch handles the research task. Keep API credentials server-side and out of published code or screenshots.

Can I customise a prebuilt workflow?

Valyu-curated templates are read-only, but supported per-run overrides can change settings such as mode and deliverables. You can also create versioned workflows for your organisation. See How to Build Your Own DeepResearch Workflow for the next step.

Start with the decision, then choose the workflow

The useful question is not “Which workflow generates the longest report?” It is “What do I need to decide, and what evidence would let me take the next step?”

Pick one template, give it a well-defined input, inspect its preview and review the result against that decision. Keep the useful structure; challenge the findings. If your next job is a company profile, clinical-trial tracker or supplier-risk map, the earlier ten-workflow guide covers those without repeating them here.

Browse Valyu's prebuilt workflows and choose the output your next research task actually needs.