Tasks

Find a task to improve.

Browse practical work across Categories. Each Task links to an AI-assisted or conventional supporting method, checks and sources.

01Reduce repetitive order-status supportEcommerceGive shoppers accurate updates from live order data. Keep unusual, sensitive, and uncertain cases with the support team.02Find and fix the causes of product returnsEcommerceConnect return reasons to products and original customer comments. Choose one evidence-backed fix to test first.03Diagnose a shipping-address checkout failureEcommerceReproduce the affected cart and address, isolate the store rule that blocks shipping, and retest one controlled change.04Reconcile checkout shipping with label costEcommerceMatch checkout charges to packages, services, labels, and surcharges before changing the store rule.05Control stock shared across product listingsEcommerceMap which products consume one component, choose the stock authority, and test every affected selling path.06Simplify custom product choicesEcommerceSeparate stock-bearing variants from custom inputs, then test whether buyers and fulfilment staff get the details they need.07Review suspicious orders before fulfilmentEcommercePreserve the order evidence, apply a human review gate, and test a narrow prevention rule against genuine checkout.08Test cross-border shipping and duty chargesEcommerceDocument what the buyer and merchant may pay, check the product and route data, and test the selected checkout path.09Verify discount combinations before a saleEcommerceDefine the intended basket price, test eligible and excluded carts, and publish terms that match checkout.10Prepare a clear, manageable preorderEcommerceChoose the order and payment state, show the uncertain ship window, and prepare a complete buyer-update route.11Plan the shipping promise for mixed cartsEcommerceTest how stocked and preorder items split, then choose a promise the checkout and fulfilment team can support.12Build a subscription dispatch queueEcommerceSeparate scheduled from overdue orders, check stock, and create a dated view for each dispatch wave.13Find new ad angles from real customer evidenceMarketingTurn customer problems, motivations, objections, and desired outcomes into distinct creative hypotheses that a person can verify and test.14Turn decisions into follow-upsOperationsYou leave the meeting with decisions to act on, but your notes don't say who owns each follow-up or when it's due.15Reconcile commitments with real capacityOperationsAccepted work exceeds the available operating time, so dates move and promises disappear without an explicit decision.16Publish asynchronous operating updatesOperationsStatus is repeated in meetings and messages, while people who miss them cannot recover the same context.17Hand off a recurring workflowOperationsAnother authorised person can own the work, yet the founder still makes every judgement and handles each exception and quality check.18Create an operational source of truthOperationsPeople cannot find the current procedure, policy, or template, and conflicting copies keep circulating.19Run a bounded operating reviewOperationsAgreed goals and measures have gone stale, so the team rebuilds status from memory after progress has already drifted.20Route internal operational requestsOperationsQuestions and approvals arrive through several channels, so ownership, required context, and decision authority remain unclear.21Automate a bounded workflowOperationsA repeated path consumes manual effort, or an existing automation has started failing without a safe exception route.22Prepare operations for a founder absenceOperationsEssential work, access, and decisions still stop when the founder is unavailable.23Coordinate an internal incident responseOperationsA security or service event has disrupted normal work while responders need one current operating picture and safe recovery authority.24Run a cross-functional launch-readiness reviewOperationsA launch date is near while dependencies, approvals, monitoring, or rollback work remain open across several functions.25Focus customer research on the next venture decisionCustomer ResearchBroad conversations are producing scattered observations. Define the decision, question, and participant group before another round.26Recruit the right people for customer interviewsCustomer ResearchOutreach is going unanswered, or convenient participants do not match the experience you need to understand.27Make it easy for early users to share useful feedbackCustomer ResearchEarly users are active, but their problems and context rarely reach the product team.28Remove bias from customer interview questionsCustomer ResearchLeading questions and solution framing are turning valuable conversations into false reassurance.29Map how customers do the work todayCustomer ResearchA proposed solution covers one step, while the wider workflow and most difficult moment remain unclear.30Find the customer segment with the most urgent problemCustomer ResearchSeveral groups sound interested, but interest alone does not show whose problem matters enough to act on now.31Watch target users try the task that mattersCustomer ResearchFeedback describes preferences, while the team still cannot see where the prototype blocks real work.32Turn customer interviews into findings you can act onCustomer ResearchNotes and transcripts are piling up, while feedback is conflicting and pointing in different directions.33Know when another customer interview will add useful evidenceCustomer ResearchInterviews are starting to repeat, but an arbitrary count cannot show whether the team missed a segment or contrary case.34Build a qualified account shortlist inside one ICPSalesTurn a chosen customer profile into a short account list with visible fit evidence, a current problem signal to test, and one next action per account.35Bound personalised outreach without losing relevanceSalesSet a small outreach batch, a fixed research brief, and review points so buyer learning does not consume every product hour.36Frame an enterprise pilot around a buyer decisionSalesDefine the buyer, problem, scope, evidence, roles, and decision that a proposed pilot must make clearer.37Triage inbound demo requests and book the next conversationsSalesTurn an avoided demo backlog into a checked queue with evidence of fit, owners, dates, and booked conversations.38Define the buyer decision path after discoverySalesTurn a useful discovery or demo into clear criteria, buyer roles, open questions, and one next step the buyer owns.39Prepare a conference conversation and agreed follow-upSalesUse a short problem-led opening, capture only agreed details, and turn a useful event conversation into a permissioned next step.40Stress-test a first B2B offer before stating the priceSalesSeparate the price structure, scope, discount, support, tax, and decision questions before presenting a reviewable offer.41Design an honest cross-language discovery workflowSalesChoose a disclosed interpreted, captioned, or asynchronous route and preserve buyer wording, uncertainty, and consent.42Diagnose a stalled enterprise deal after the demoSalesRebuild the stakeholder and decision map, test the next step with the buyer, and mark the deal as advance, pause, or close.43Maintain a minimum sales record after every callSalesKeep promises, buyer priorities, unresolved questions, and one owned next action together without turning administration into a second job.44Choose which product concept deserves coded investmentProductSeveral plausible concepts are competing for scarce product and engineering effort after the problem research is complete.45Define the smallest usable MVP boundaryProductThe proposed first release exceeds the team’s capacity, yet removing more work could leave the core user path incomplete.46Set an investment appetite before solution work expandsProductA raw product idea is expanding before the team has decided how much capacity the problem deserves.47Find feasibility risks before committing the buildProductA shaped solution looks coherent, but an unresolved design, technical, contractual, or regulatory dependency could invalidate it.48Write a product brief that supports an investment decisionProductThe product concept lives in conversations and sketches while reviewers need one shared basis for a resource decision.49Reprioritise the product roadmap with displaced work visibleProductNew requests compete with work already in progress, while every item is described as urgent.50Turn an incoming feature request into a product decisionProductA proposed implementation is being treated as the requirement before the underlying workflow failure is clear.51Define the success signal and measurement plan before releaseProductThe team can ship the change, but it cannot yet tell whether the intended product outcome improved or regressed.52Plan a limited release with an explicit stop decisionProductA change is ready for real use, while broad exposure could reveal a product or operational problem too late.53Decide what to do with an unused product featureProductA shipped feature shows weak use while it still adds maintenance, support, and future product constraints.54Establish your positioning before creating campaign assetsMarketingTurn existing audience, product, and competitor evidence into one internal statement that guides later marketing work.55Diagnose and revise a landing-page messageMarketingTurn a weak landing page response into a testable message hypothesis without treating a sign-up count as product validation.56Choose a bounded acquisition-channel experimentMarketingCompare a small set of plausible acquisition routes, select one affordable test, and record the evidence needed for a stop, revise, or continue decision.57Prepare a Launch HN or Show HN product launchMarketingMatch a launch story, product access, proof, and response plan to the documented Launch HN or Show HN rules.58Build a search-led content plan from supported audience questionsMarketingMap supported audience questions to useful pages, a publishing order, and later search evidence.59Send a useful welcome message to new subscribers or usersMarketingGive an eligible recipient one clear next step, a truthful help route, and a reviewed way to record response.60Agree a co-marketing brief with a niche partnerMarketingDefine a shared audience asset, partner value, responsibilities, approvals, and a safe distribution route.61Review channel evidence against a campaign decisionMarketingConnect a campaign decision to its channel evidence, data gaps, competing explanations, and recorded next action.62Turn a vague support message into a clear next actionCustomer SupportCapture the missing context, choose an owner, and give the customer a realistic next-update time.63Turn a resolved question into reusable support knowledgeCustomer SupportSearch existing knowledge, improve the closest answer, or publish a new checked article without customer-specific facts.64Capture support messages in one reviewable queueCustomer SupportConnect the channels the team can monitor, assign every active item, and test the path from message to acknowledgement.65Set a clear client support owner and update cadenceCustomer SupportDocument who owns support, which channel to use, ordinary hours, and when the client should expect the next update.66Acknowledge after-hours messages while holding a support boundaryCustomer SupportPublish working hours, define genuine urgent exceptions, and acknowledge when the queue will be reviewed.67Define what support can answer and when to escalateCustomer SupportClassify routine issues, create checked responses, and require a context-rich handoff for risky or unknown cases.68Investigate a customer complaint and offer a proportionate resolutionCustomer SupportRecord the complaint, check promises and evidence, decide a suitable remedy, and send a calm response with a next step.69Make and communicate a final reimbursement decisionCustomer SupportReview the customer refund request, evidence, policy, and applicable rules before communicating one final decision and escalation route.70Respond to a negative public review without escalating itCustomer SupportVerify the case, publish a short factual response, and move personal details or resolution work to a private channel.71Publish reliable incident updates while the fix proceedsCustomer SupportAssign one communication owner and maintain one current status with impact, phase, and next-update time.72Keep a dated cash forecast current as facts changeFinanceReplace a hopeful bank-balance view with dated receipts, obligations, estimates, and the periods that need a decision.73Review a new commitment against dated cash obligationsFinanceModel a proposed commitment beside expected receipts and existing obligations before recording a proceed, delay, reduce, or decline decision.74Build an itemised spend view that reconciles to the booksFinanceGroup recorded spend by established accounts and keep unknown, personal, duplicate, or unsupported items in a visible review queue.75Resolve overdue invoices before the next client contactFinanceVerify balances, disputes, payments in transit, contact history, and the next authorised action before sending a reviewed reminder.76Match customer deposits to invoices and isolate exceptionsFinanceTrace each deposit to a customer payment and invoice while separating fees, partial payments, duplicates, and corrections for review.77Capture expense evidence before the monthly matchFinanceCollect the purchaser, vendor, date, amount, purpose, account, approver, and receipt while the transaction is still recognisable.78Prepare a reconciled handoff for your accountantFinanceAgree the period and package, reconcile the included accounts, list open items, and grant only the access the accountant requests.79Investigate a reconciliation difference without forcing a correctionFinanceMatch the statement one item at a time, test common causes, and send uncertain edits or prior-period changes to an accountant.80Control team purchase access and trace each transactionFinanceRecord who may buy, for what purpose, within which limit, and how every purchase reaches an approver and the statement match.81Define a role from the work that needs to movePeopleTurn recurring founder work into outcomes, tasks, boundaries, entry competencies, and evidence that interviewers can use consistently.82Run a candidate pipeline with visible next actionsPeopleGive each active candidate a documented stage, owner, next action, evidence link, and timely status.83Structure interviews around comparable job evidencePeopleAsk the same ordered job-related questions and capture evidence against human-approved anchors.84Reconcile a written job offer before sending itPeopleCheck approved role, terms, conditions, dates, and decision ownership before an authorised person sends one proposal.85Prepare a new hire to start with clear supportPeoplePrepare approved access, essential context, role outcomes, first-week work, named help, and check-in dates.86Delegate work with clear authority and boundariesPeopleRecord the outcome, context, authority, constraints, evidence, timing, and escalation route, then invite correction.87Set decision rights for one founder decisionPeopleAssign the driver and one final approver, then list the contributors, informed people, and escalation route for one decision.88Run a private one-to-one with a shared agendaPeopleReview priorities, blockers, feedback, support, and agreed actions in a restricted agenda both people can shape.89Give feedback from observed behaviour and impactPeoplePrepare specific situation, behaviour, and impact evidence, ask for the other person’s view, and agree the next check.90Test adviser fit before discussing equityPeopleDefine the needed contribution, run a bounded working trial, check references, and record scope before a long-term commitment.91Set the current company directionStrategy & FundingProducts, markets, or initiatives have accumulated without one current choice about whom the company serves and what it will stop.92Compare company financing pathsStrategy & FundingThe company needs resources, while the founder cannot yet see how feasible financing paths affect control, disclosure, timing, and company shape.93Prepare a bounded investor outreach listStrategy & FundingThe company has chosen a counsel-approved securities process and needs to identify possible investors without drifting into uncontrolled solicitation.94Trace every investor pitch claimStrategy & FundingA pitch is being prepared, but its metrics, calculations, assumptions and disclosures still need to be checked against the same evidence trail.95Run an investor conversation recordStrategy & FundingInvestor conversations create repeated questions, documents, commitments, and follow-ups that pull several founders away from operating work.96Prepare an investor diligence recordStrategy & FundingA serious investor requests evidence, while document ownership, completeness, exceptions, and disclosure limits are unclear.97Compare financing offer questionsStrategy & FundingOne or more term sheets or SAFEs differ in structure, control, conditions, and counterparties, while valuation alone hides important questions.98Prepare an investor update for reviewStrategy & FundingA reporting date or material event requires a consistent account, while disclosure duties, facts, risks, and recipient boundaries need review.99Record a pivot-or-persevere decisionStrategy & FundingA strategy is missing its stated evidence, while more initiatives could consume the time or capital needed to make a deliberate change.100Review capital-partner alignmentStrategy & FundingThe company’s chosen path conflicts with investor expectations, rights, or time horizon, and repeated conversations have not produced one shared record.