# Sponsor a Feature ✨

**SA5 has been under development for 6 years, and its development is largely directed by the needs of Sygnal's clients and the projects we're working on.** 

Occasionally, library users request special features or enhancements that aren't currently on our roadmap, or that we're planning, or that are under development but which we haven't needed to implement yet. 

{% hint style="success" %}
**UNDER DEVELOPMENT** \
In these docs, feature pages marked with a green test-tube 🧪 in the title are experimental and under-development.  These are likely already built in our own code bases, but not redesigned as attributes for the general public,, tested, or fully documented. 

*These are the closest features to completion.* 
{% endhint %}

Now you can sponsor the development of those features, and they will be added to the library for everyone to use.  

## How much?

Cost depends on the feature, complexity, and our availability, but for many feature additions it would be quite low, in the $100 to $300 range.

You get;

* The feature you need
* The awesome feeling of supporting other Webflow devs around the world 
* Our thanks, and a credit to you listed on that feature page 

**If you're interested, drop a message in SA5's Forum ( link at top ), and we can discuss.** 

{% hint style="info" %}
Please note that sponsored features must make sense for the community as a whole and must be compatible with SA5's engineering roadmap.  If yours is not, it can still be developed for you privately as a site-specific feature just for your project. 

See our [Webflow development & micro-consulting](https://www.sygnal.com/webflow) options for details. 
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://attr.sygnal.com/overview/sponsor.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.