1) There is certainly value, but I would consider this a vitamin, not a painkiller.
2) Options if they were to pick something off the shelf would be $500/mo minimum. Quality is slightly less than what they're getting with us.
3) Annual contract, we would provide updates at a tbd interval.
4) We definitely have an opportunity to price in additional support. Whether they choose to use it or not, it would make the license price seem more reasonable.
1. Not many competitors, but each competitor offers about a $500/mo plan that allows ~10 users.
2. We have greater accuracy and detail in our analysis. This has been proven with sample data and they agree that this is true.
3. $500/mo seems too much on the low-end for this. I'm not sure what "high" would be for a bank.. $5k, $10k?
4. I would like to bill this as an annual contract with monthly, quarterly, or annual payments. Current SaaS users are billed monthly or annually. Since they'll be self-hosting this, they will be responsible for user management and access. I will not have access to their internal systems.
The root of the pricing problem is we charge based on usage. If they self-host, we won't be measuring that usage as the tool will run without network connectivity.
Price for competitive value, start where you think, but
- tier it to bundle of users at least, so as more users are added any additional effort on your part has financial cover
- think about support, customer success, installation, upgrades and ensure your including that
- test the number with them. Negotiate.
Caveat - this is limited advice use at own risk etc etc
We're a consulting company looking to hire on a full time developer for one of our clients, a B2C online tournament provider.
We're looking for someone VERY strong with AWS who could champion a project of leveraging other AWS services and improving the overall system architecture.
Knowledge of .NET MVC is also crucial.
Bonus points if you have some front-end skills, but this is definitely more of a back-end centric role.
Broadway Lab, Inc. | Austin, TX OR REMOTE (United States or Mexico) | Full-time & Contract | Software Engineers, All Levels | https://broadwaylab.com
Broadway Lab is a consulting firm that specializes in building software for early stage companies & enterprises.
We're looking for engineers familiar with the following technologies:
- SPAs (React, Angular, View.js)
- React Native
- Native iOS + Android
- Ruby on Rails
- .NET/C#
We're also hiring an Engineering Director if you're at a point in your career where you want to manage a team of developers.
Why work with us?
We are a distributed team that values a good work/life balance. If you get tired of working in the same codebase all of the time, then you'll be a good fit working with here.
Full-time engineers preferred, but we're open to contractors for the right situations.
We’re currently about 15 employees and looking to double this year!
If you're interested, send us an email at hello@broadwaylab.com.
Broadway Lab is a consulting company focused on iOS, Android, and Rails development.
We're looking for a full-time Junior iOS developer. The team is remote, but we're based in Austin, TX. You'll be working with our clients and internal projects (roughly a 70-30 split).
If interested, send a quick email with your github, links to recent apps you've worked on, and where you're located to michael@broadwaylab.com. Must be based in the United States.
I still live in fear of the day some time down the road when all the people far smarter than me start writing articles titled "Why Function/Reactive/Reactifluxidux architecture was a horrible decision". That's the nature of tech I suppose.
It is always a horrible decision and often driven by an incompetent management not to go native. If I'd ask my aces to use react, I am pretty sure at least one would puke over the desk, another one would jump out of the fifth floor and the rest would simply decline and start question my competencies. (I know you'd puke Felix!)
On the other hand we're earning a lot due to all the unnecessary and wasted resources we have to sell to meet performance expectations of our customers ( and those guys happily buy it ) you could reach with 1/1000 probably 1/100000 of the MIPs by utilizing native C.
Utilizing react is not even programming or engineering. That's assembling. rant off
you're going to get downvoted and you'll think it's because you badmouthed a popular technology. It's not because of that, it's because you criticized something on a technical forum without giving any concrete reasons why said technology is bad.
Well, we can't know the future, but I'd like to draw a parallel. A few years ago, Java offered the promise "write once, run anywhere". It worked pretty well until a major OS decided "nah, not gonna happen here".
What's different this time?
It is popular (Java was and still is), it is backed by a big company (Java too), it only needs Javascript, which all devices have (Java only needs a JVM, which all devices used to have).
Well, I sure hope for all the folks involved it really is the future. At least, it may well be for the next few years.
> It worked pretty well until a major OS decided "nah, not gonna happen here".
No, it really didn't. For a time after "Java Web Start" was introduced in 2001, java had (has) a pretty decent story for distributing application (big run time dependency, problematic java updater non withstanding).
But I think the biggest problem java had/has is the mix of java being a hopelessly verbose, and arguably rather primitive language that's a bad fit for both AWT and (to a lesser degree) Swing. It's almost comical to contrast "hello world" with swing/java and with swing/jython (or jruby) - it's not that the UI toolkit is unusable, but it's not a good fit for the biggest use-case: simple business applications.
I should add that I think kotlin looks like a pretty perfect match for "the good parts of java without any added complexity".
> What's different this time?
Modern JS is arguably a better fit for simple GUI programming than modern java is.
Just like on the desktop, true native apps will always have their place on mobile. But for a very large majority of apps React Native will be more than good enough and much faster to work with.
Personally I've switched my focus from native iOS to React & React Native.
I can't say I don't miss types, but if you use ESLint and FlowType it's not as bad as you might think. Hopefully I'll be able to start using Typescript on React projects soon.
It totally sounds like the future, but I can't help but hate the fact that it is tied to javascript. React-native with WASM would be a dream come true :)
I personally use scala.js and clojurescript quite a bit, but in every case of an existing non-JS language compiling to JS, there is a semantic mismatch coming from the runtime mismatch. This results from various things like the lack of static types, threads, 64 bit integers, etc. Furthermore, the performance still leaves a lot to be desired.
WASM holds a lot more promise for all of these problems.
Required skills: Native Android development and experience with Bluetooth LE.
The project is building a native Bluetooth LE plugin for a Unity app. API for the device the app communicates with is fully documented, and there's an existing iOS plugin to help guide you if necessary.
Please reach out to michael@broadwaylab.com. Thank you!
I agree REITs are great - especially if you're busy and don't have time to manage a property. However, it's important to invest in a REIT with a track record ('O' is a good example). These things go under all of the time. Managers get paid based on the asset base and have no skin in the game. Common for smaller funds to be shut down.
