Funding and backing
Worker budget target $1,500
Card authorization is a temporary hold, not payment. It can transfer to the bounty and be cancelled before Work Orders and the allocation certificate are locked at work start.
Before card authorization, sponsors see the maximum total including the worker budget, platform service fee, payment processing, and any applicable tax.
Primary action
Sign in to add interestRequests collect scope and backing interest first. A builder can claim work only after this converts to a funded bounty.
What should be built
A small web app that turns uploaded invoices into a review queue with vendor, due date, amount, and follow-up status.
- Target users
- Not recorded on this earlier request
- Product owner
- Not recorded on this earlier request
- Delivery
- Public GetAppBuilt GitHub repository
What counts as done
- Upload CSV or PDF invoice samples
- List invoices with vendor, amount, due date, and status
- Mark follow-up complete
- Export CSV
Constraints
Add details.
Non-goals and risk boundaries
- No payment credentials. No automatic bank access. No production email notifications.
Request details
GitHub/manual handoff
No GitHub issue required yet
Request progressScope, risk, backing, conversion, and release handoff.Handoffs
Risk review. Not run for the current scope. Review is advisory by default; only an explicit hard policy decision blocks funding, issue linking, or conversion. A risk decision never authorizes funding, capture, payout, identity, or publication.
- available
Request scope review
Owner: lead sponsor or request owner
- available
Run AI/risk filter
Owner: risk reviewer
- next
Add funding interest
Owner: sponsors
Backers can register funding interest until the funding target is secured or the request converts into a funded bounty.
- next
Draft or link backing GitHub issue
Owner: request owner, verified maintainer, or GetAppBuilt operator
The request owner, a verified repository maintainer, or a GetAppBuilt operator must create or link a reachable issue. Invalid, private, or inaccessible links return to that authorized owner.
- waiting
Convert to bounty
Owner: lead sponsor or request owner
Conversion requires repaired scoped terms, a backing issue, and funding target readiness.
- waiting
Prepare delivery handoff
Owner: GetAppBuilt operator
Delivery handoff waits for a converted bounty and accepted deliverable.
Issue handoff. The request owner, a verified repository maintainer, or a GetAppBuilt operator creates or links the reachable issue. Issue authors wait unless asked for context; a valid accessible issue unlocks conversion, while access errors return to that authorized owner. Writing the issue does not grant funding, merge, refund, payout, or approval authority.
Backing issue draft
[GetAppBuilt build request] Invoice follow-up assistant
Build request: Invoice follow-up assistant Requested outcome: A small web app that turns uploaded invoices into a review queue with vendor, due date, amount, and follow-up status. Acceptance criteria: - Upload CSV or PDF invoice samples - List invoices with vendor, amount, due date, and status - Mark follow-up complete - Export CSV Constraints: - No constraints were recorded on this earlier request. Non-goals: - No payment credentials. No automatic bank access. No production email notifications. Funding status: - Backing interest (not payment): $100. - Card authorized (not captured): $0. - Verified funding: $0. - Effective funding: $0 of $1,500. - Remaining to secure: $1,500. GetAppBuilt policy: - This issue draft does not create verified funding. - Workers can claim only after this request converts into a funded bounty. - Accepted source is delivered in a public repository in the GetAppBuilt GitHub organization. - GetAppBuilt does not provide customer hosting, domains, production infrastructure operation, or long-term maintenance. Build request id: build_req_8bf3f0cf7bd14dc2b9