I haven’t worked with them in a consulting capacity like you’re describing, but I have met with some of their team in general discussions. They are genuinely skilled Fusion developers, and exactly the partners I would want in your shoes.
As a Fusion dev, here’s some expectations on those scenarios that I would set if you were working with me.
- No info here, I haven’t worked with that kind of automation myself yet
- Auto-route based on logic is reasonable as long as you can clearly define the logic. Auto-routing based on capacity is a mine-field of complexity.
- This is usually reasonable as long as the information to populate the project details either exists in the originating request or can be programmatically determined from it.
- Potentially difficult, depending on how you are able to determine which project(s) those tasks belong inside, and what you need them to do once they’re created. (Assign people automatically, have predecessors, planned hours, durations etc). Auto-tagging is something reasonable as long as who should be tagged is clearly available.
- No info here, I haven’t worked with that kind of automation myself yet
I would definitely expect any developer to be able to ask discovery questions like I just did above and estimate level-of-effort from there to make informed decisions with you before beginning to use development hours. Determining how many scenarios can be built within a certain number of hours isn’t really possible until the scope of the scenarios is fully defined. I have production scenarios I built in 30 minutes, and I have others that took weeks of effort.
I see that you tagged ‘third-party integration’ also, and that can be a basket of worms all by itself if you need off-platform integrations outside of Workfront.
From there, I would anticipate lots of really granular questions as the outline of the scenario develops. I can outline what I would be asking for one of your scenarios if that’s helpful?
Katherine
