Linear Reviews

Precoro Reviews

1. Andrii

   · co-founder at Effy · about 4 years ago
   PRs, POs, invoices, vendor catalog - all in one system

   We can track each purchase order, who created it, and why. They are no longer lost, and we can always see the history. The dashboard allows us to monitor information about all essential documents and at what stage they are now and keep track of which invoices have not yet been paid or partially paid. By setting up budgets for each department, we can effectively plan the allocation and prevent overspending. The system is very flexible and convenient. I can't imagine my work without it.

   🏁 Competitors: Procurify

   👍 Pros:    Reimbursement management|Purchase order management|Supplier management|Financial reporting|Handy dashboard|Ease of use

   👎 Cons:    I'm satisfied with the way precoro handles its task. there are a few things that could be automated. for example, editing multiple pos at once
2. dkulaksyz

   · PM at Stripo Inc · about 4 years ago
   Easy onboarding and great value for money

   I easily plan budgets for each project, promptly track spending, and create custom reports. Precoro allows doing this in 2 clicks. All suppliers and items are in one place, so purchase requests and orders are quickly created without errors. Precoro is a cloud-based tool, so I can use it from any device as long as I have internet. This greatly speeds up approval time and helps me keep everything under control no matter where I am.

   🏁 Competitors: Procurify

   👍 Pros:    We'll never go back to excel spreadsheets again. one solution meets all our needs and even more. visible approval workflow, budget section for each department, custom reporting fields, and item catalog make purchasing very easily manageable.

   👎 Cons:    Nothing, everything that becomes an issue is easily taken care of by their customer success team.
3. Amy

   · Operations Manager at Expandi · about 4 years ago
   Very helpful software, easy to use!

   Each employee has access to Precoro at least for purchase requisition creation. This is very convenient because the budgets of each department are visible to their employees. Attachments and comments can be added to the requisitions, and items are added directly from the loaded catalog. All subsequent docs (from purchase order to receipt) are created automatically, significantly saving time. All statuses can be tracked in real-time and are always correct. The approval process is customizable; creating 1 or more stages to comply with the company's rules is possible.

   🏁 Competitors: Procurify

   👍 Pros:    High level of adaptation to the specific processes of each company or department|Customer support team to help set up processes, conduct employee training, and solve all related issues.|Saving time for all employees by automating and speeding up the ordering process|Precise cost analytics for efficient planning and budget management|Improved communication with the finance department

   👎 Cons:    We didn't have the option to add attachments when creating a vendor, but precoro fixed that in the last update.

Linear mentions (162)

• The Tradeoff That Slows Production Teams Down: Flexibility vs Actually Shipping

  Speed matters. Not speed in sprint or linear dashboards. Not speed in story points. - Source: dev.to / about 2 months ago

• Freshworks Just Shipped an MCP Gateway Inside Its ITSM Platform. Here's What That Actually Changes.

  Model Context Protocol, for context, is the emerging standard for letting AI agents pull live data from external systems without custom integration code. Freshworks has implemented it as a native layer in Freddy AI, which means agents can now reach into Notion, ClickUp, Linear, Workday, Rippling, and the rest of the enterprise stack — not through brittle webhooks or bespoke connectors, but through a standardized... - Source: dev.to / about 2 months ago

• How to Document and Track Technical Debt

  Issue trackers: GitHub Issues, Linear, or Jira work well because technical debt records live in the same tool as feature work. This makes them easier to pull into sprint planning and keeps the debt backlog visible alongside the feature backlog. The main risk is that debt issues get buried under feature issues without careful labeling and triage discipline. - Source: dev.to / about 2 months ago

• How to Write a Technical Debt Remediation Plan for Non-Technical Stakeholders

  Linear and similar tools can track velocity metrics per area of the codebase over time, making the before/after comparison straightforward to document. - Source: dev.to / about 2 months ago

• Master the in demand of salary negotiation and system design: What Fails

  Most engineers fail salary negotiations because they use vague statements like "I work hard" or "I’m a good teammate" instead of quantified, verifiable impact. After 15 years of negotiating offers, I’ve found that engineers who tie their ask to concrete business outcomes land 30% higher offers than those who don’t. For example, instead of saying "I improved the API", say "I reduced API p99 latency by 400ms, which... - Source: dev.to / 2 months ago

Precoro mentions (0)