> For the complete documentation index, see [llms.txt](https://guide.updraft.fund/updraft/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.updraft.fund/updraft/basics/drafting-a-solution.md).

# Drafting a Solution

Once you have a concrete plan to implement an Idea, you can draft a Solution from an Idea page.

<figure><img src="/files/6WzsqFQnuzPqEiMWxJcU" alt="" width="375"><figcaption><p>Draft a Solution from an Idea Page</p></figcaption></figure>

{% hint style="info" %}
You may already have a Solution in mind when you create an Idea. It's perfectly fine to draft a Solution to your own Idea.
{% endhint %}

## Funding parameters

When drafting a Solution, you'll need to answer the following questions.

* How much funding do you need?
  * You can raise a small amount to accomplish the first milestone of your Solution and then extend the funding goal and deadline.
* What token do you want people to fund with? (The default is UPD.)
  * Choose a token that will be convenient for funders. Everyone on Updraft will already have UPD. You can also choose a token with a stable value (a stablecoin) to make sure the goal amount doesn't change during the fundraising period.
* How much time do you need to raise the required funds (deadline)?
  * Shorter deadlines are attractive to funders because they know they can get a refund sooner if the goal fails.
* How many tokens should you 💎 stake?
  * A stake is an optional way to increase the chance of funding by offering an additional reward if the goal isn't met.
* How high should you set the 🎁 funder reward?
  * A funder reward allows funders to earn a percentage of contributions that come after theirs. Setting this is a balance between rewarding funders and leaving more for your Solution.

{% content-ref url="/pages/ueAZCJYMLcQgXIfeBVW9" %}
[Funder rewards](/updraft/basics/funder-rewards.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://guide.updraft.fund/updraft/basics/drafting-a-solution.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.