SMF·WRIKE
Can a prompt replace Wrike?
Project management — work management with request intake
Exhibit tracking slip
Verdict
Wrike's distinguishing feature is the front door: a request form that becomes a structured task in the right folder with the right owner, and an approval step with a decision that is recorded rather than remembered. Building the intake-to-approval chain properly is a week, mostly because branching forms and approval state are fiddlier than they look. It is a kinda, not a no — the gaps are mobile apps, proofing on files, and the enterprise controls, none of which is a moat.
Exhibit A — The prompt
Received on31.07.2026Build a request-intake and approval system with a task tracker attached, in that order of priority.
Stack: your choice, Postgres, Docker Compose, a domain with TLS so the public form can live on it.
Request forms:
- A form builder with fields (text, long text, select, multi-select, date, number, file upload) and **branching**: a question can reveal or hide later questions based on an answer. Branch conditions are stored as data and evaluated identically on the client and the server — validating only on the client is how a public form gets filled with impossible combinations.
- Submission mapping: each form declares which project the task lands in, which fields map to which task fields, who the default assignee is, and which approval chain applies. That mapping is the feature; without it a form is just a spreadsheet with extra steps.
- Public submission with a token or captcha, an emailed confirmation to the requester containing a tracking link, and file uploads validated by type and size.
Approvals:
- An approval chain is an ordered list of steps, each with one or more approvers and a rule of any-one or all-of.
- A task in approval is locked for editing on the fields under review, and the lock is shown with a reason.
- Each decision records approver, decision, timestamp and comment, permanently. A rejection returns the task to the previous step with the comment attached and is never erased by a later approval.
- A deadline per step, with a reminder before it and a visible overdue state after — no auto-approval, ever. Silent auto-approval defeats the purpose of an approval.
Tracker underneath: folders and projects, tasks with assignee, dates, status and custom fields, a table view and a board view, and dependencies.
The requester's tracking link shows status and approval progress without a login, on an unguessable token, and shows nothing but that.
Write tests for branch evaluation agreeing between client and server, for all-of versus any-one approval, for rejection returning to the previous step with history intact, and for the tracking token exposing nothing beyond the request.
Do not build proofing, resource planning, or mobile apps.Opening prefills the prompt — press enter to run it.
Exhibit B — What you lose
- B.1 the mobile apps
- B.2 proofing and mark-up on images, video and PDFs
- B.3 resource and capacity planning across teams
- B.4 the enterprise controls — SSO, audit, retention, custom roles
- B.5 the integration catalogue and two-way syncs
Prior art
Exhibit C — Why people still pay: intake and approval workflow
Because the intake form is what stops work arriving as a chat message, and because an approval nobody can later dispute is worth more to a marketing or creative team than any board layout.
Questions
Why evaluate branching on the server as well?
Because a public form can be submitted by anything, not just your JavaScript. Client-side branching is a convenience; server-side evaluation is what makes the resulting data trustworthy.
Why refuse auto-approval on a deadline?
Because the entire value of an approval is that somebody is accountable for it. A step that approves itself after five days is a record that nobody decided, which is worse than no record.
What is the tracking link for?
It stops the "any update on my request?" email. An unguessable token that shows status and nothing else costs an hour and removes a whole category of interruption.
Does Wrike export cleanly?
Tasks and folders export to Excel, and the API covers the rest. Approval history is the part to extract deliberately — it is the record with the longest useful life and the least obvious export path.
Related tools
Receipt